Return range in the lint result
See original GitHub issueCurrently ESLint returns the line
and column
when linting. However, with editor plugins it would be useful to get the full range so instead of just visually showing where the violation starts it could mark the whole range of the violation.
For example, here the Atomlinter ESLint plugin could use the range instead of just marking the first character.
<bountysource-plugin>
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>
Issue Analytics
- State:
- Created 8 years ago
- Reactions:1
- Comments:21 (19 by maintainers)
Top Results From Across the Web
Working with Rules - ESLint - Pluggable JavaScript Linter
- returns the cwd passed to Linter. It is a path to a directory that should be considered as the current working directory....
Read more >Linters | golangci-lint
Name Description Presets Since
asasalint ⚙️ check for pass any as any in variadic func(...any) bugs 1.47.0
bidichk ⚙️ Checks for dangerous unicode character sequences...
Read more >go - How to use pointers or indexing on a range to resolve ...
I'm getting the following output when running https://golangci-lint.run/: rangeValCopy: ...
Read more >4.6 lint Reference and Examples (Sun Studio 12
Across files, lint detects cases where a non-void function does not return a value, yet is used for its value in an expression—and...
Read more >Lint :: RuboCop Docs
Ranges are handled by Lint/AmbiguousRange . ... In this situation, the return will result in an exit from the current method, possibly leading...
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
Yes, I will do. I’m sorry, I’m busy for now. I think I can get time within the next month.
The implement of this issue has done in #6640. Tweaking of core rules remains.