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.
Update coding standards and decide which should be enforced by Eslint
See original GitHub issueWhen I created the Webpack build, I transferred the linting mechanism from jshint to Eslint carrying over as best as I could the jshint rules from the old build. It wasn’t clear to me whether or not the jshint rules had been enforced by the build (ie the build fails if a rule is broken) so I left the linting as advisory.
Can we discuss and agree which (if any) rules we want to enforce, which we want to appear as a warning, and whether we want to mention and justify these in CONRIBUTING.md?
I can then updated the Eslint rules as agreed.
Issue Analytics
- State:
- Created 4 years ago
- Comments:15 (4 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 recommend https://standardjs.com/ for eslint
If we want to enforce the rules, it should break the build. Just like the e2e tests do.