-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Feature Request] Support for multiple scopes #14
Comments
Yeah ! I checked their source code is done using
If he doesn't choose he can't go to the next question
I think borrowing can be done with |
@Zhengqbbb https://github.com/faressoft/inquirer-checkbox-plus-prompt - such library actually already exists 😃 (or maybe I just misunderstood your comment about "writing the one myself" 🙈) |
LOL, once my own personality starts, I will write all the inquirers myself 🤯. |
need turn on option: `enableMultipleScopes` link #14
Hey bro ! @jaklan
Now yet I haven't added tests yet to make sure the checkboxes work, I need to add tests later |
@jaklan Hi, The latest version 🌟(v1.3.1)🌟 checkbox=1 cz
# same it can turn on emoji mode
emoji=1 cz |
Hello @Zhengqbbb, sorry for a late response, I've finally found some time to test multiple scopes - and they work really nice, thank you! |
Great 🤗 Thx u response ~ |
💭 Describe the feature
commitlint
provides support for multiple scopes:https://commitlint.js.org/#/concepts-commit-conventions?id=multiple-scopes
When you use
@commitlint/cz-commitlint
adapter, you can enable support for that incommitizen
as well by providing the following options incommitlint
config:https://commitlint.js.org/#/reference-prompt?id=settings
Then, you can select multiple scopes in
commitizen
withspace
and confirm withenter
. If empty scopes are forbidden, if no scope is selected you get the hint you need to select at least one to continue.💡 Proposed Solution
To respect the above configuration. The one issue I see is the fact that in
cz-git
space
is used as input tosearch
, but imho in that case we can "override" its behaviour to select the scope instead - scopes with spaces are rather rare use-case, so imho such a compromise should be quite acceptable. Or we can just think about another keystroke to trigger scope selection / unselection (right arrow
to select,left arrow
to unselect?).The text was updated successfully, but these errors were encountered: