You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to cause an eslint error I have defined an explicit issue in my file .gql (I've reduced it to the relevant parts only):
query GetUser() {
users {
id
aFalseField
}
}
But when I run my eslint pages/** I have no error related to graphql/template-strings.
So I have used eslint with debug mode : eslint pages/** --debug and I have this kind of errors :
Eslint parse all .gql but it seems have a conflict between @typescript-eslint/parser and eslint-plugin-graphql
And if I add 'extraFileExtensions: ['.gql']' in my config I have no conflict but still no lint errors as well ..
Note :
The problem is only for separate files, when I use the graphql-tag eslint works well and detect aFalseField
const query = gql `
users {
id
aFalseField
}
`
The text was updated successfully, but these errors were encountered:
alexis-regnaud
changed the title
No errors from an invalid mutation or query
No errors from an invalid mutation or query (Error @typescript-eslint/parser)
May 19, 2020
Hi,
I am trying to use the
eslint-plugin-graphql
but it doesn't catch my graphql error.Here's my eslintrc.js (I've reduced it to the relevant parts only) :
In order to cause an eslint error I have defined an explicit issue in my file
.gql
(I've reduced it to the relevant parts only):But when I run my
eslint pages/**
I have no error related tographql/template-strings
.So I have used eslint with debug mode :
eslint pages/** --debug
and I have this kind of errors :Eslint parse all .
gql
but it seems have a conflict between@typescript-eslint/parser
andeslint-plugin-graphql
And if I add 'extraFileExtensions: ['.gql']' in my config I have no conflict but still no lint errors as well ..
Here my packages version :
Note :
The problem is only for separate files, when I use the graphql-tag eslint works well and detect
aFalseField
The text was updated successfully, but these errors were encountered: