-
Notifications
You must be signed in to change notification settings - Fork 934
Feature request: support more options for scope-case rule #70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
The addition makes sense, let's add it. Some comments.
Rules that should support new cases Cases to support
A PR would be awesome! |
The options should be on Examples taken from @commitlint/config-angular. |
Let's go with |
Will release with 4.0 in the next days |
Released via 4.0! 🚀 |
bpedersen
pushed a commit
to bpedersen/commitlint
that referenced
this issue
Oct 15, 2019
…log#70) Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.1.1 to 4.1.2. - [Release notes](https://github.com/wycats/handlebars.js/releases) - [Changelog](https://github.com/wycats/handlebars.js/blob/master/release-notes.md) - [Commits](handlebars-lang/handlebars.js@v4.1.1...v4.1.2) Signed-off-by: dependabot[bot] <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! I want camelCase as scope-case rule. I think we can use lodash to avoid coding. Like:
https://lodash.com/docs/4.17.4#camelCase
https://lodash.com/docs/4.17.4#kebabCase
https://lodash.com/docs/4.17.4#snakeCase
And, we could throw an error if an invalid option is set? I think defaulting to lowercase is not good.
If you think that this approach is ok, I can try to make a PR with this feature.
Best.-
The text was updated successfully, but these errors were encountered: