-
Notifications
You must be signed in to change notification settings - Fork 129
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
graphql-js 16 support #625
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/theguild/envelop/D3SMeCZWLAdP21dZvs5im8Axi8qv |
🦋 Changeset detectedLatest commit: d4a4ce6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest changes of this PR are available as alpha in npm (based on the declared
|
✅ Benchmark Results
|
0aeb54b
to
fc369ef
Compare
f59d557
to
08d8bb1
Compare
08d8bb1
to
9995ca5
Compare
9995ca5
to
981d4be
Compare
981d4be
to
84c2bae
Compare
Run tests for both GraphQL.js 15 and 16 ✅
issues:
Conflicts with Types GraphQL.js 15
subscribe (Now solved ✅ )
subscribe
changed return type usages fromAsyncIterableIterator
toAsyncGenerator
. I cast those to AsyncGenerator within the code.Parser (PR pending 📝 )
GraphQL.js 16 added types for
Parser
, thus I had to remove the declarations for the v15 Parser definition. This results in v15 build complaining about missing types. We need to find a way to conditionally add definitions for Parser when running v15 builds or ad a lot lot lot of ts-ignore statements.I figured out the easiest way would be to just have those type-definitions within GraphQL.js 15, so I created a PR over here: graphql/graphql-js#3251
GraphQL.js 16 Tests
graphql-jit is not compatible with GraphQL.js 16
The plugin fails with the following error:
ApolloServer using the legacy
execute(schema, ...args)
call signature which makes it incompatible with GraphQL.js 16 (Now solved ✅ )This breaks
useApolloServerErrors
with the following error, this must be fixed in Apollo, which imports execute from graphql-js directly.Created apollographql/apollo-server#5662 for fixing this and also apollographql/apollo-server#5663 for addressing the ignored TypeScript errors.
ALso added a mock in the tests so we don't need to wait for those upstream changes.