feat(engine): add support for custom scopes option #216
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change is to support the custom scopes definition in the package.json's `config.commitizen.scopes` key. The format of the key matches the format of the `config.commitizen.types` key. Each scope has a `description` and `title` key used by inquirer to display the scope to the user. In order to maintain backwards-compatibility, the default value for the new package.json key (i.e., `scopes`) is an empty JSON object. When no keys are present in this object, we will default to custom user input for the scope. This also includes the option to press Enter to skip. refs: #213
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is to support the custom scopes definition in the package.json's
config.commitizen.scopeskey. The format of the key matches the format of theconfig.commitizen.typeskey. Each scope has adescriptionandtitlekey used by inquirer to display the scope to the user. In order to maintain backward-compatibility, the default value for the new package.json key (i.e.,scopes) is an empty JSON object. When no keys are present in this object, we will default to custom user input for the scope. This also includes the option to press Enter to skip.refs: #213
cz-conventional-changelog-support-custom-scopes.mp4