-
Notifications
You must be signed in to change notification settings - Fork 185
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
Clean-up: use expect_no_lint() where appropriate #2737
Labels
internals
Issues related to inner workings of lintr, i.e., not user-visible
Comments
Maybe we can do a staged effort for this again by applying on the lint-changed-files workflow only until it's resolved? |
This was referenced Feb 13, 2025
Merged
This was referenced Feb 21, 2025
This was referenced Mar 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
expect_no_lint()
is a nice alternative toexpect_lint(., NULL, .)
. We should use it where possible.This will be a relatively large lift: there are about 1,500 call sites to
expect_lint()
withNULL
:We could also introduce a linter for this, but I reckon it's too localized to warrant a new export. We can add it as a custom local linter to our suite I reckon.
The text was updated successfully, but these errors were encountered: