Problem with setting operations property on parserOptions when no operations in .graphql files

Issue workflow progress

Progress of the issue based on the Contributor Workflow

• 1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox

Please make sure the graphql-eslint version under package.json matches yours.

• 2. A failing test has been provided
• 3. A local solution has been provided
• 4. A pull request is pending review

---

Describe the bug

We don’t have operations defined inside of .graphql files. They are all defined in .ts and .tsx files. If I set my config as:

  overrides: [
    {
      files: ['*.ts', '*.tsx'],
      processor: '@graphql-eslint/graphql',
    },
    {
      files: ['*.graphql'],
      extends: ['plugin:@graphql-eslint/operations-recommended', 'plugin:@graphql-eslint/relay'],
      parserOptions: {
        operations: './src/**/*.{ts,tsx}',
        schema: '../api-server/src/schema.graphql',
      },
    },
  ],

then I get the following errors in each of the .tsx files

If I remove the operations property from parserOptions, then I get the following error for a number of rules:

Error: Error while loading rule '@graphql-eslint/require-id-when-available': Rule `require-id-when-available` requires `parserOptions.operations` to be set and loaded. See https://bit.ly/graphql-eslint-operations for more info

I’m not sure how to proceed without running into errors or disabling a lot of rules.

[takumiya081]

@B2o5T I try it and works fine 🎉 thank you ❤️

[nikolaik]

I had a legacy .graphqlconfig taking precedence over parserOptions that cased similar issues like described in the original post. After adding the following parserOptions all was well:

parserOptions: {
  skipGraphQLConfig: true
}