Feature - Option to disable "validate against schema"

[jgoux]

Hello all 👋

Now that there is the awesome https://github.com/dotansimha/graphql-eslint for doing linting and validation against a schema directly as part of ESLint, I'd like to use the vscode extension only for the purpose of autocompletion and code navigation.

Actual Behavior

At the moment, both ESLint and the extension are validating my operations :

In term of performance, the work is done twice. Also we can go further with ESLint by enforcing conventions and even writing custom lint plugins.

Expected Behavior

I'd like to have a validate against schema (default true) configuration option for this plugin so I can use it to enhance my DX in VSCode, but defer all my validation and linting to ESLint.

Specifications

• GraphQL for VSCode Extension Version: v0.3.14

[jtieu-r7]

Running into a similar issue, are there any solutions for this?

[acao]

hmm, hadn't thought of this! a feature could be added as such. I think it could be added to just this repo, and the answer is in extension.ts for the curious!

[arvindell]

This sounds like what I need. I would like to disable schema validation to tweak the rules that my tagged template literals are validated against. vscode-graphql doesn't seem to support toggling on/off.

This rule, for example, has had a bug for a while and I don't have a way to ignore the error without losing autocompletion and highlighting 😕

[zachallaun]

I'm running up against the same fragment issue as @arvindell above. Would love to see an option to disable this kind of validation.