[lsp-server] 🐞 JS/TS files should only be checked when included in `documents` config glob

[echocrow]

[lsp-server] 🐞 JS/TS files should only be checked when included in `documents` config glob

[acao]

re: this, this problem has been fixed in a PR last month, the stage 2 rewrite of the LSP server, after releasing the first rewrite today, I will then prepare this other branch to consolidate all of this in stage 2 rewrite. TLDR i have spent about 400 hours preparing several rewrites to address this and many more issues!

you just need to make the directives available via introspection!

and if not you can add them to the graphql config

[echocrow]

cheers for the context, and all the hard work! sounds a fix for this is already in the pipeline. 🤞

if it's of any help, when available I'm happy to test the LSP rewrite for the issue reported here.

you just need to make the directives available via introspection!

totally agree if it was just directives!
unfortunately the unexpected GraphQL LSP checking goes beyond directives thogh. piggybacking the repro from the OP, which demonstrates other tooling features:

• When using e.g. gql.data, we can leverage separate Fragment definitions in JS. Those could be co-located, or could be shared and imported from other JS files. However, GraphQL LSP complains about the unknown fragment when used in another query. Given what the LSP knows, that makes sense; I don't know think it would be in GraphQL LSP's scope to understand and validate this rather tooling-specific setup.
• The tool in this repo comes with its own autocomplete suggestions in the form of a TS plugin. With the GraphQL LSP also running in the same JS/TS file, however, they two unexpectedly compete. This results in a flood of duplicate query/mutation/field suggestions. Not critical, but a minor annoyance, and potentially a bit confusing at first.