eslint-plugin-graphql icon indicating copy to clipboard operation
eslint-plugin-graphql copied to clipboard

:vertical_traffic_light: Check your GraphQL query strings against a schema.

Results 101 eslint-plugin-graphql issues
Sort by recently updated
recently updated
newest added
trafficstars

I have 2 sets of graphql files that apply to different schemas. These are distinguished via different extensions (something like): `Foo.apiOne.graphql` `Bar.apiTwo.graphql`. I'd like to configure the ESLint for graphql-literal...

In using this tool, I've noticed that every error simply says that the eslint rule violated is `"graphql/template-strings"`. It'd be nice if violations of the rules would explicitly state which...

Consider the following use case: On the UI, a list of several items with a checkbox next to each one. You activate a number of check boxes, then click a...

I've tried both 'apollo' and 'literal as the 'env' setting. Should it use the schema defined in my .graphqlconfig file? The docs are not 100% explicit and I'm not getting...

**Intended outcome:** Detect that `resendUserVerificationInput` is supposed to be Non-Null in this query: ```graphql #import "fragments/mutationResponseFields.gql" mutation ResendVerification($input: resendUserVerificationInput) { resendUserVerification(input: $input) { resendUserVerification { user { id phoneNumber }...

In our project we have graphql queries in file format `query.js` i.e apollo and newer ones in `query.graphql` so we would need specify an array of environments for our rules...

Previously, only one half of the branch checked that `type` existed; now both do. (Have triggered this error, but not figured out specifically what query causes it yet.) TODO: -...

Hi i'm using [`@connection`](https://www.apollographql.com/docs/react/advanced/caching.html#connection-directive) directive but `graphql/template-strings` rule throws an error like the below ``` error Unknown directive "connection" ``` Query ```js const QUERY = gql` query Community($offset: Int, $limit:...

I enabled this plugin today, and when I run eslint, I get the following warning on the console: ``` { parser: "babylon" } is deprecated; we now treat it as...

this should prevent questions like this one: https://github.com/apollographql/eslint-plugin-graphql/issues/84 which I had to find for myself.