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

Jump to bottom

When misspelling the blueOak category name, it doesn't warn me #46

Closed
ronkorving opened this issue Mar 28, 2019 · 1 comment · Fixed by #87
Closed

When misspelling the blueOak category name, it doesn't warn me #46

ronkorving opened this issue Mar 28, 2019 · 1 comment · Fixed by #87

Comments

@ronkorving
Copy link

I think missconfiguration should be rather fatal, as it can be hard to validate (especially on small projects with few dependencies) that the test that is running is actually correct. It may give false positives. It would be nice if, when passing a blueOak value of foo, it would throw an error saying that is not an existing category.
@kemitchell
Copy link
Member

Send me a PR?

@ericcornelissen ericcornelissen mentioned this issue Dec 1, 2022
Merged
@kemitchell kemitchell mentioned this issue Dec 1, 2022
Draft
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check for misspelled blueOak categories
2 participants
@kemitchell @ronkorving