Preprocessing error on invalid 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 When typing in new code in a file makes it temporarily invalid Javascript/Typescript, IntelliJ will show an error banner with “ESLint: Preprocessing error”. This only happens with this plugin enabled, and stops happening if I add a try/catch block in the preprocessor in https://github.com/B2o5T/graphql-eslint/blob/fffb1273f5eda8e3ff3ff15da52202c02be19639/packages/plugin/src/processor.ts#L14

To Reproduce

1. Configure a project to use Eslint and this plugin.
2. Open a file in that project that has syntax errors in IntelliJ.

Expected behavior No error banner should be shown, similar to how other plugins handle invalid files.

Environment:

• OS: Windows 10
• @graphql-eslint/eslint-plugin: 3.10.7
• eslint: 8.23.1
• Node.js: 16.13.2
• IntelliJ: 2022.2.2

[Lugribossk]

Awesome, thank you for the fix!

And I think it makes sense to see the error in the terminal, since you run that when you want to know about errors. While the banner shows up when you’re in the middle of editing a file.

[B2o5T]

I guess we can back try/catch statement, so the annoying popup in WebStrom will disappear, anyway ESLint will report about the problem while running eslint in terminal

before

after

fixed in @graphql-eslint/eslint-plugin@3.11.1