Unknown fragment in vscode's graphql extension (LSP) when using client-preset with fragment masking

[eddiew]

I'm using graphql-code-generator with client-preset, and overall it's working well for me. The types are generated correctly and I'm able to use fragment masking as recommended in the guide.

My issue is just related to tooling. I'm using VSCode's graphql extension to get auto-completion for graphql queries, and for some reason it can't find the fragment definitions, so most of my files have these "errors" in them.

I've looked thru existing discussions a bunch of times and couldn't find anything on this. Maybe someone can help me?

[Urigo]

Thank you for reporting, can you share a reproduction we can try to run with the extension?

[eddiew]

Sure, I'll work on finding a minimal repro. So I take it that not many others have run into this issue then?

…

On Sun, Nov 19, 2023 at 9:28 AM Uri Goldshtein ***@***.***> wrote: Thank you for reporting, can you share a reproduction we can try to run with the extension? — Reply to this email directly, view it on GitHub <#9748 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANSNRJXRE2FA24K2HTKXA3YFIJRDAVCNFSM6AAAAAA66F2LVWVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TMMJRGQ2DG> . You are receiving this because you authored the thread.Message ID: <dotansimha/graphql-code-generator/repo-discussions/9748/comments/7611443@ github.com>

[eddiew]

Found the solution from this comment thread: #8554 (comment)

Basically, my problem was because I was using include instead of documents in my graphqlrc to specify which files to look at