Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Report format: log number of fixable problems
See original GitHub issueI’m using eslint v3.7.1.
One of my favourite eslint features is the ability to fix a lot of problems automatically. When my team considers adding a new eslint rule, we take into account how many times the rule is broken and whether those new problems can be fixed automatically. So sometimes we want to know how many problems can be automatically fixed without actually running eslint with the --fix option.
The current report ends with something like this:
✖ 103 problems (103 errors, 12 warnings)
It would be great if the number of fixable problems was also included. Maybe like this:
✖ 103 problems (103 errors, 12 warnings).
88 errors, 2 warnings can be fixed by running eslint with the --fix option.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’d rather not race to get things into 4.0. This has been sitting for a while without any progress, trying to quickly revive it seems like a bad idea, especially when there doesn’t appear to be any implementation decision.
TSC resolution: Issue has been accepted. See meeting notes for details (labelling as breaking for now)