-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
/*jshint ignore:start*/ does not ignore W101 "Line is too long." #1575
Comments
This was fixed with bf886b8. |
It seems that issue still appears when using grunt-contrib-jshint v0.11.0 which uses jshint v ~2.6.0 |
you are right. test case:
|
may be also fixed by #2477 |
not fixed by #2512 or earlier patches |
This is still happening for me in 2.9.2
We use a .jshint.rc file in our case. But using /* jshint -W101 */ before the line does work, so this isn't urgent for me. |
This is not fixed yet |
@englishextra I cannot reproduce the erroneous warning in JSHint version 2.9.2 |
Well the idea is to hide masonry lib from linting https://gist.github.com/englishextra/f1cc7d27876773f206081a2fd261be01 In my case it appears not to ignore the commented code https://gist.github.com/englishextra/f1cc7d27876773f206081a2fd261be01 |
Region of code marked with
/*jshint ignore:start*/ ... /*jshint ignore:end*/
in JSHint 2.4.4 still may produce warning "Line is too long." for commented lineCode to completely ignore warnings in some region of code looks like
The text was updated successfully, but these errors were encountered: