-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Idea: support "nolint ranges" #129
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
Comments
I would like to see this implemented. My use-case: disable |
Stale bot went rampant. @jirfag please reopen. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
That's still a problem. |
@AlekSi is there a reason you're not able to do:
|
A better exemple coud be: // Save provides a complex save method using third-party library with really long method names.
func Save() {
...
very long line of code //nolint:lll
...
another very long line of code //nolint:lll
...
one more //nolint:lll
...
} |
@AlekSi I appreciate that other use cases exist, I was asking if my suggestion works for your specific challenge above. |
I have just had the experience of ignore I'm thinking of doing ignore as follows.
Please give your opinions on this idea. (And other opinions are also verrry welcome.) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Revive has the concept of begin/end blocks for nolinting. See here.
This could be useful under some circumstances.
The text was updated successfully, but these errors were encountered: