Skip to content
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

Closed
wants to merge 1 commit into from
Closed

chore: support graphql-js@16 #1983

wants to merge 1 commit into from

Conversation

acao
Copy link
Member

@acao acao commented Oct 14, 2021

This is just a start on upgrading to graphql-js@16!
Typescript builds, there are just some issues with tests now... potentially regressions?

TODO:

  • codemirror mock is suddenly failing in tests?!? see: Codemirror.hint failures
  • @defer and @stream built-in directives are missing from autocompletion unit tests, so we might need to switch to the graphql@16.0.0-rc.4-experimental-stream-defer tag
  • mergeAST cypress tests are expecting a newline at the end that isn't there anymore due to a breaking change across versions
  • incrementalDelivery cypress test is failing because no @defer or @stream is present

@changeset-bot
Copy link

changeset-bot bot commented Oct 14, 2021

⚠️ No Changeset found

Latest commit: 5900909

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

const deprecationWarningAnnotations = mapCat(
findDeprecatedUsages(schema, ast),
validate(schema, ast, [NoDeprecatedCustomRule]),
Copy link
Member Author

@acao acao Oct 14, 2021

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

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions
Copy link
Contributor

@github-actions github-actions bot temporarily deployed to graphiql-1 October 14, 2021 09:40 Inactive
@github-actions
Copy link
Contributor

@github-actions github-actions bot temporarily deployed to monaco-graphql October 14, 2021 09:41 Inactive
@acao acao mentioned this pull request Oct 24, 2021
Copy link
Member

@IvanGoncharov IvanGoncharov left a 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,
Copy link
Member

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

@acao
Copy link
Member Author

acao commented Oct 29, 2021

closing for #1988

@acao acao closed this Oct 29, 2021
@thomasheyenbrock thomasheyenbrock deleted the chore/upgrade-graphql-16 branch June 1, 2022 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants