Skip to content

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

Closed
navarroaxel opened this issue Sep 5, 2017 · 6 comments
Closed

Feature request: support more options for scope-case rule #70

navarroaxel opened this issue Sep 5, 2017 · 6 comments
Labels

Comments

@navarroaxel
Copy link

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.-

@marionebl
Copy link
Contributor

The addition makes sense, let's add it.

Some comments.

  • Let's stick with the current default to avoid breaking changes

Rules that should support new cases

Cases to support

  • camelCase
  • PascalCase
  • kebab-case
  • snake_case
  • Start Case

A PR would be awesome!

@navarroaxel
Copy link
Author

The options should be on kebab-case (ex. present-imperative) or camelCase (ex. lowerCase)?

Examples taken from @commitlint/config-angular.

@marionebl
Copy link
Contributor

Let's go with kebab-case, but continue support for lowerCase, upperCase.

@marionebl
Copy link
Contributor

@marionebl
Copy link
Contributor

Will release with 4.0 in the next days

@marionebl
Copy link
Contributor

Released via 4.0! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants