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.
Suggestion: Enforce 80 character lines with Eslint
See original GitHub issueDescribe the problem and steps to reproduce it:
Whilst working on #4693, multiple reviewers mentioned that my lines exceeded 80 characters and thus were too long, however eslint did not complain. For example, here is 95 characters long.
To reproduce the problem, simply type out any valid line of code that is greater than 80 characters in length.
What happened?
yarn lint did not report any errors with lines > 80 characters.
What did you expect to happen?
yarn lint should complain when lines are > 80 characters and the build should fail on CI.
Anything else we should know?
It looks like the currently .eslintrc configuration extends from amo - that would be a good place to begin investigations.
In addition, it might be worthwhile to use Prettier pre-commit hooks to automatically format code when commits are made based on the existing eslint config.
Issue Analytics
- State:
- Created 5 years ago
- Comments:8 (8 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
Fixed by #5313
FWIW Prettier got a lot better lately with more config options like
--arrow-parensand a nice integration with eslint.