Skip to content
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

Issues with "type_scope_conventions" #778

Open
adaniloff opened this issue Jun 25, 2020 · 2 comments
Open

Issues with "type_scope_conventions" #778

adaniloff opened this issue Jun 25, 2020 · 2 comments

Comments

@adaniloff
Copy link

Q A
Version GrumPHP 0.15.2
Bug? yes
New feature? no
Question? no
Documentation? yes

Hi there, 2 issues:

  1. Documentation issues about type_scope_conventions
type_scope_conventions:
  - types:
    - build
    - ci
    - chore
    - docs
    - feat
    - fix
    - perf
    - refactor
    - revert
    - style
    - test
  - scopes: []

should be (both for type and scope i doc btw):

type_scope_conventions:
  types:
    - build
    - ci
    - chore
    - docs
    - feat
    - fix
    - perf
    - refactor
    - revert
    - style
    - test
  scopes: []

Otherwise the conf is not loaded.

  1. enforce_capitalized_subject does not work well with type_scope_conventions defined:
  • "fix: Some capitalized subject" ----------> fails (but should not)
  • "Fix: some uncapitalized subject" ------> succeed (but should fail)
@veewee
Copy link
Contributor

veewee commented Aug 27, 2020

The first issue has been handled in more recent versions. You don't need both keys set anymore.
The second issue is harder. The type scope convention part is detached from the check that validates that the subject has a capital. I don't think that will be something we can fix easily without rethinking how the task works internally.

Feel free to provide a PR.

@adaniloff
Copy link
Author

Yeah I had a little look so I understand why is it harder to resolve :)
If I got some time at any point, I'll try.

Thanks for your reply, have a good day :)

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

No branches or pull requests

2 participants