Closed orsenkucher closed 2 years ago
Ok, so I've downloaded .tgz
from npm graphql-language-service-server
of version 2.5.6
and it doesn't contain needed fix
Published https://marketplace.visualstudio.com/items?itemName=orsenkucher.vscode-graphql And it works on Windows 😱🤯😎🥳🤪
Creating a PR might be a good idea to get the maintainers to check this out. I'm curious why you added codemirror and change the typescript dependency though https://github.com/orsenkucher/vscode-graphql/commit/06fbd5fec23be82a5622bc1e315e564f95550f00#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519
We just need a PR to update our language server to use our latest LSP release! This repo will soon be merged with graphiql repo to make this part easier. If someone wants to create a PR just to update the language server to our latest version that would be rad
this should be released now! let me know if there are issues
this should be released now! let me know if there are issues
I am still having this issue, I cannot use go to definition as it just says unable to resolve reference
Are the files that contain fragments listed in documents
?
Are the files that contain fragments listed in
documents
?
Yes, VS Code says it's unable to resolve the resource and lists the exact path of the file.
Sorry for some of the path being drawn over as this is the only image I have as I'm not on my PC, but that's the exact path the file is in.
Hello, please bump
graphql-language-service-server
dependency from^2.5.6
->^2.5.7
or later or update.lock
files Because, as my investigation has shown current dependency setup does not contain changes from https://github.com/graphql/graphiql/pull/1715Thus I don't have
Go to Definition
navigation working, the URI of file resource to open is malformed for windows.Steps to reproduce:
npm install
node_modules\graphql-language-service-server\dist\MessageProcessor.js\MessageProcessor\handleDefinitionRequest
and atln: 438
your should seeIf you run from
Debug
->Extension
now, code navigation won't work on windows.yarn.lock
,package-lock.json
andnode_modules
npm install
againln: 440
you will seeWhich is now correct and everything works as expected 🥰