We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Hi @ivome!
I've tried to update graphql-query-complexity to support graphql-js v14 but I got this error while running the tests:
graphql-query-complexity
graphql-js
(...) \graphql-query-complexity\node_modules\graphql\validation\validate.js:89 throw new Error(errors.map(function (error) { ^ Error: Unknown directive "complexity". Unknown directive "complexity". Unknown directive "cost". Unknown directive "complexity". Unknown directive "complexity". Unknown directive "complexity". at assertValidSDL (...)
Because v14 is making better validation of the schema/query: https://github.com/graphql/graphql-js/releases/tag/v14.0.0
Can you take a look at your test suite and maybe update readme to add info about the demand of registering directives explicitly? 😕
The text was updated successfully, but these errors were encountered:
f47d05c
Just upgraded the library to support graphql-js v14. New version is published on NPM
Sorry, something went wrong.
Thanks! 🎉 You could just add || ^0.14.0 to not making a breaking change as it's doesn't seem to be needed.
|| ^0.14.0
Allow graphql-js 0.13 #13
cf335c8
Done! 😉
No branches or pull requests
Hi @ivome!
I've tried to update
graphql-query-complexity
to supportgraphql-js
v14 but I got this error while running the tests:Because v14 is making better validation of the schema/query:
https://github.com/graphql/graphql-js/releases/tag/v14.0.0
Can you take a look at your test suite and maybe update readme to add info about the demand of registering directives explicitly? 😕
The text was updated successfully, but these errors were encountered: