eslint-disable-line directive still errors for exceeding max-len
See original GitHub issue1; // eslint-disable-line
---
rules:
max-len: [2, 1]
index.js
1:0 error Line 1 exceeds the maximum line length of 1 max-len
✖ 1 problem (1 error, 0 warnings)
Expected the directive to allow exceeding max-len rule.
Issue Analytics
- State:
- Created 9 years ago
- Comments:15 (5 by maintainers)
Top Results From Across the Web
How to disable eslint rule max line length for paragraph in ...
I am using airbnb eslint and currently I am getting error: error: Line 6 exceeds the maximum line ...
Read more >Error Codes and Messages - PVX Plus Technologies
Cannot exceed pre-set maximum size for user work space (set either using a -SZ option or in the START directive). Free some of...
Read more >max-len - ESLint - Pluggable JavaScript Linter
/*eslint max-len: ["error", { "comments": 65 }]*/ /** * This is a comment that violates the maximum line length we have specified **/....
Read more >List of the armcc error and warning messages - Arm Developer
An open #if was still active, but was not closed with #endif before the end of file. 38 : directive is not allowed...
Read more >Troubleshoot Dataflow errors | Google Cloud
This error occurs if your job's graph size exceeds 10 MB. ... If it is still too large, try executing the Dataflow job...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
May you please create a new issue and fill out the bug report template? If this bug still exists, it will probably get more attention in a new issue.
@zachlysobey May you please create a new issue and fill out the bug report template? If this bug still exists, it will probably get more attention in a new issue.