We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
function() { do_something # nolint start: one_linter. edge_case_stuff() # nolint stop: one_linter. }
will throw the lint on # nolint stop. this seems less than ideal but I'm not sure if it can be easily fixed.
# nolint stop
The text was updated successfully, but these errors were encountered:
Maybe never lint COMMENT nodes?
COMMENT
Sorry, something went wrong.
Actually comments were one of the things I definitely wanted to lint. Often see things like
function() { do_something() # print(x) }
i.e., vestigial comments that should probably be removed (or at least moved away from the very end of the function)
Shouldn't that be a separate lint message at least? Trailing comments aren't exactly unreachable code.
Also, just to clarify, these lints are excluded by exclude(), right?
exclude()
Oh, good point. Edited the issue -- they're not excluded because they're specific to a different linter.
Successfully merging a pull request may close this issue.
will throw the lint on
# nolint stop
. this seems less than ideal but I'm not sure if it can be easily fixed.The text was updated successfully, but these errors were encountered: