-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
chore: support graphql-js@16 #1983
Conversation
|
const deprecationWarningAnnotations = mapCat( | ||
findDeprecatedUsages(schema, ast), | ||
validate(schema, ast, [NoDeprecatedCustomRule]), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this change will require us to depend on graphql@15.4.2
? or later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good, all changes are expected and were planned for the v16 release.
I would recommend updating peerDependencies
to drop v14 and support only latest v15 and 16.0.0
.
@@ -37,6 +37,7 @@ function createEditorWithHint() { | |||
return CodeMirror(document.createElement('div'), { | |||
mode: 'graphql', | |||
hintOptions: { | |||
hint: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@acao Is it related to graphql@16
?
It looks like it causes this error:
https://github.com/graphql/graphiql/runs/3892946205?check_suite_focus=true#step:5:28
closing for #1988 |
This is just a start on upgrading to graphql-js@16!
Typescript builds, there are just some issues with tests now... potentially regressions?
TODO:
@defer
and@stream
built-in directives are missing from autocompletion unit tests, so we might need to switch to thegraphql@16.0.0-rc.4-experimental-stream-defer
tagmergeAST
cypress tests are expecting a newline at the end that isn't there anymore due to a breaking change across versionsincrementalDelivery
cypress test is failing because no@defer
or@stream
is present