Repository navigation
@graphql-eslint/eslint-plugin does not work with frolint cli #926
Description
Why
In the following .eslintrc, use yarn eslint . /src will work, but yarn frolint -branch master -bail will raise an error.
.eslintrc
{
"overrides": [
{
"files": [
"*.tsx",
"*.ts"
],
"extends": "wantedly-typescript",
"parserOptions": {
"project": [
"./tsconfig.json",
"./tsconfig.eslint.json"
]
}
},
{
"files": [
"*.tsx",
"*.ts"
],
"processor": "@graphql-eslint/graphql"
},
{
"files": [
"./src/profile/components/profile/Sidebar/RelatedUsers/**/*.graphql"
],
"parser": "@graphql-eslint/eslint-plugin",
"parserOptions": {
"schema": "./graphql-gateway-schema.json"
},
"plugins": [
"@graphql-eslint"
],
"rules": {
"@graphql-eslint/fields-on-correct-type": [
"error"
]
}
}
]
}Internal Error: Error while loading rule '@typescript-eslint/no-floating-promises': You have used a rule which requires parserServices to be generated. You must therefore provide a value for the "parserOptions.project" property for @typescript-eslint/parser.
Occurred while linting /path/to/project/src/path/to/Component.tsx/0_document.graphql
Activity
izumin5210 commentedon Sep 14, 2021
cc @prsdta @tkeiyama
qnighy commentedon Sep 14, 2021
So we may need an option to turn off rules that require type-aware linting?
prsdta commentedon Sep 14, 2021
Indeed, just changing the
rulestoseems to fix the error. But I would like something more future-proof that does not require to disable manually all rules 🤔
prsdta commentedon Sep 14, 2021
@graphql-eslintalso seems to usetypescript-eslintinternally, so we shouldn't need to disable it all.It seems to be more an issue with applying our default rules with the
graphql-eslintparser.See this comment in a related issue: https://github.com/dotansimha /graphql-eslint/issues/544#issuecomment-891948697