The specifications are:
<type>(<scope>):<subject> #header
// 空一行
<body>
// 空一行
<footer>
1. The header part has only one line, including three fields: type (required), scope (optional), and subject (required).
type is used to describe the category of this commit, and only the following 7 identifiers are allowed:
- feat: new features (feature)
- fix: fix bug
- docs: modify documentation (documentation)
- style: format (do not change the code logic)
- refactor: refactoring (that is, it is not a new feature, nor is it a code change to modify a bug)
- test: Modification of the test case
- chore: changes in the build process or auxiliary tools (not src and test)
- build: Change the build process, add dependent libraries, tools, etc. (for example, webpack modification)
- perf: Modifications to improve performance and performance
- ci: automatic process configuration modification
- revert: roll back to the previous version
Scope is used to describe the scope of the commit's influence, such as the data layer, control layer, view layer, etc., depending on the project.
Subject is a short description of the purpose of the commit, no more than 50 characters.
2. The body part is a detailed description.
3. If Footer is not compatible with the previous version, it starts with BREAKING CHANGE, followed by a description of the change, the reason for the change, and the migration method.
BREAKING CHANGE: isolate scope bindings definition has changed.
To migrate the code follow the example below:
Before:
scope: {
myAttr: 'attribute',
}
After:
scope: {
myAttr: '@',
}
The removed `inject` wasn't generaly useful for directives so there should be no code using it.
If this time you submit for an issue, you can close the issue at Footer.
Close #5612
Closes #6523, #56846