graphql-voyager
graphql-voyager copied to clipboard
ESLint as linter
The roadmap mentioned to adopt eslint
. The adoption of eslint
has definitely a bit value, but it requires the agreement on three major points:
- Which
eslint
setup shall we have? - Which plugins should we use?
- How deep do we want to go with error fixing?
I did a first test with draft PR #234 and as expected it showed many errors, only 50% fixable. @joeponzio was suggesting to consider AirBNB rules, which I did.
Before fixing errors, do we agree with the current eslint
setup? Is there any other plugin do I need to consider/add?
Let's discuss
I suggest first start with "recommended" preset from ESLint and then move forward.
How deep do we want to go with error fixing?
Ideally you just disable rules that triggered errors and enable it one by one in a separate commits (can by one PR but separate commits).