Add eslint checks for graphql files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11
- Forks
- 26
- Avg merge
- 11h 58m
- Merged PRs (30d)
- 16
Description
### Is your feature request related to a problem?
Whenever I run ```npx eslint ```, I am starting to get warnings.
### Describe the solution you'd like
If team feels this is something that needs fixed, we could:
1. ```npm install --save-dev @graphql-eslint/eslint-plugin```
2. Add a new override section to the .eslintrc.json (or equivalent config file) specifically for *.graphql files to use the graphql parser and plugins.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the repository's .eslintrc.json or equivalent configuration and the GraphQL files that produce warnings with `npx eslint `. Review the proposed @graphql-eslint/eslint-plugin setup, then confirm that running ESLint on those files no longer reports the described warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- eslint, graphql, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100