-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@playlyfe/gql doesn't work with version of "graphql" > "0.11.7" #97
Comments
It should work with versions below 0.12. We are working on getting better support for all graphql versions soon. |
I've tried graphql-for-vscode/src/server/server.ts Line 68 in e52efb0
Is there something I can help with on this? It's kinda surprising that with GraphQL being used more and more these super useful tools have lost people interested in maintaining them. |
Hi @FredyC, we have a branch for working with |
@kumarharsh I would definitely like to help to get this moving. The extension helped me a lot before, but our backend guys decided to use I guess the first step would be to figure out to use that compatible branch and have it loaded in the VSCode, shouldn't be that hard hopefully. |
Ok, guys, I want to thank for all the hard work and the joy this extension has brought in the past 👏 It's time to move on with the awesome Apollo GraphQL that has emerged. It works out of the box without any complicated configuration and extra packages. I really recommend you to try it out. |
@FredyC Sadly it doesn't support referencing a local schema consisting out of several files which I really need. |
@levrik Then file the suggestion. Apollo is surely a more active community and there are good chances for that to happen. |
If the package.json use the latest version of graphql.js package, you have the following error:
[Info - 10:42:06] NODE_PATH value is: xxxxxx
[Error - 10:42:08] Server initialization failed:
Request initialize failed with message: Cannot find module 'graphql/validation/rules/ArgumentsOfCorrectType'
Using "graphql": "0.11.7" fix the problem...
The text was updated successfully, but these errors were encountered: