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.
Evaluating recommended ruleset
See original GitHub issueIs your feature request related to a problem? Please describe.
At the current project I am working on, we are in the process of evaluating a recommended ruleset for our usage of graphql-eslint, since there is none yet unfortunately. The project is quite big with 50+ packages in a monorepo structure, so this plugin will have a great impact (thanks for making it!)
Basically, around 5-7 people in our team will vote on keeping or removing rules for our ruleset and then we will agree on the final ruleset. I can post the resulting ruleset here, then it could be further discussed and potentially implemented in graphql-eslint as recommended to make devs work easier!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:9 (2 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
Sure thing, the least I can do for using such a great library!
It will still take a couple of days until all relevant devs will decide on the ruleset, then I will let you know right away.
Yes, seems good, I’ll split recommended config into two configs
schema-recommendedandoperations-recommended. We can do a major release with them and new options fornaming-conventionrule