[lsp-server] 🐞 VSCode validation error Unknown fragment in v0.11.0

[minami-minami]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I get errors after updating “GraphQL: Language Feature Support” to v0.11.0.

• FooFragment is defined another file.
• No errors if defined in the same file.

Expected Behavior

No errors when using fragments from another files.

Steps To Reproduce

1. define fragment
2. define query or fragment in another file.
3. use fragment defined in step 1

Environment

• LSP Server Version: latest
• OS: macOS 13.5.1
• LSP Client: VSCode v1.89.1
• graphql: v16.8.1

Anything else?

No response

[sbiallas]

I have the same problem. I use GraphQl-Codegen with the client preset, which works as expected. I get syntax highlighting and autocomplete options inside the gql tags. But when I use fragments from other files their are not recognized. I had these fragments also working, also with the fragment names showing up as autocomplete options, but I can't reproduce it. When I rename the generated gql tag to e.g. graphql and adjust the imports suddenly the errors disappear and I get also the right autocomplete options, but after next reload of vscode the errors are there again and autocomplete stops working. I got error messages inside the LSP output for I guess every file which contains a gql tag:

[jordanweaver]

I also noticed this behavior and it was even more subtle in my case... all I had to do was simply open the file containing the fragment and then the error disappeared in the file/query where the fragment was spread. But it would come back with any reload or edit.

Not sure how recommended it is, but I opted to manually downgrade through VS Code's extension manager, where it seems 0.9.3 was the last version prior to 0.11.0:

[sbiallas]

I also noticed this behavior and it was even more subtle in my case... all I had to do was simply open the file containing the fragment and then the error disappeared in the file/query where the fragment was spread. But it would come back with any reload or edit.

Not sure how recommended it is, but I opted to manually downgrade through VS Code's extension manager, where it seems 0.9.3 was the last version prior to 0.11.0:

Did the same and worked for me!

[VinceBT-BG]

This is kind of a breaking bug, all fragments have broken in my project as well

[pronovaso]

Confirm same bugs as mentioned here.