Skip to content

feat(@graphiql/plugin-doc-explorer): migrate React context to zustand, replace useExplorerContext with useDocExplorer and useDocExplorerActions hooks #3940

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

Merged
merged 10 commits into from
May 11, 2025

Conversation

dimaMachina
Copy link
Collaborator

No description provided.

@dimaMachina dimaMachina mentioned this pull request May 9, 2025
30 tasks
Copy link

changeset-bot bot commented May 9, 2025

🦋 Changeset detected

Latest commit: 8a55062

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@graphiql/plugin-doc-explorer Minor
graphiql Patch

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

@dimaMachina dimaMachina marked this pull request as ready for review May 11, 2025 11:36
@dimaMachina dimaMachina merged commit 5a66864 into graphql:main May 11, 2025
14 checks passed
@acao acao mentioned this pull request May 11, 2025
@mjfwebb
Copy link

mjfwebb commented Jun 17, 2025

@dimaMachina I think perhaps the versioning change on this PR was incorrect. It seems this was a breaking change as you renamed most of the exported code in packages/graphiql-plugin-doc-explorer/src/index.tsx which results in consumers of the code needing to make changes.

@dimaMachina
Copy link
Collaborator Author

@dimaMachina I think perhaps the versioning change on this PR was incorrect. It seems this was a breaking change as you renamed most of the exported code in packages/graphiql-plugin-doc-explorer/src/index.tsx which results in consumers of the code needing to make changes.

@graphiql/react still use 0.x. According to Semver is valid to introduce breaking changes in 0.x releases

@dimaMachina dimaMachina deleted the v4-2 branch June 17, 2025 11:11
@mjfwebb
Copy link

mjfwebb commented Jun 17, 2025

@dimaMachina I think perhaps the versioning change on this PR was incorrect. It seems this was a breaking change as you renamed most of the exported code in packages/graphiql-plugin-doc-explorer/src/index.tsx which results in consumers of the code needing to make changes.

@graphiql/react still use 0.x. According to Semver is valid to introduce breaking changes in 0.x releases

Right! I didn't see that 👍

@dimaMachina
Copy link
Collaborator Author

@dimaMachina I think perhaps the versioning change on this PR was incorrect. It seems this was a breaking change as you renamed most of the exported code in packages/graphiql-plugin-doc-explorer/src/index.tsx which results in consumers of the code needing to make changes.

@graphiql/react still use 0.x. According to Semver is valid to introduce breaking changes in 0.x releases

Right! I didn't see that 👍

Feel free to try out graphiql 5.rc, release this month!

Blogpost with migration guide in graphql/graphql.github.io#2015

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