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

Linter should not report "excellent condition" when issues/warnings found #633

Open
1 task done
mattwthompson opened this issue Jul 17, 2024 · 1 comment
Open
1 task done
Labels

Comments

@mattwthompson
Copy link
Member

Solution to issue cannot be found in the documentation.

  • I checked the documentation.

Issue

The linter, and its behavior as documented to maintainers reports "excellent condition" even when it finds things it doesn't like.

I just wanted to let you know that I linted all conda-recipes in your PR ({}) and found it was in an excellent condition.

These shouldn't both be the case, especially when multiple suggested changes are communicated. Sometimes these changes are not, in fact, optional. Maintainers can read into this contraction whatever they wish, which isn't something a linter should allow.

I suggest the language be scaled back closer to "good" when something is found, or possibly "acceptable" when there are several issues.

Installed packages

N/A

Environment info

N/A
@beckermr
Copy link
Member

Thank you for this issue!

Another way to think about the language here is that we have been informally using linter hints as a location for what are more accurately described as "future lints." We may want to make that distinction explicit as well.

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