0.22.0 and 0.22.1 seems to have undocumented breaking changes, how should the community proceed with the upgrade? #3600
Unanswered
klippx
asked this question in
Q&A / Support
Replies: 2 comments 1 reply
-
thanks for this @klippx ! I'm sorry you're having this issue. you tagged the right people, we will check it out! currently our example implementations of this API are static and don't include stateful hooks, which we should fix! I can confirm this was working when I fixed the Saleor GraphiQL instance last fall |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hey @klippx 👋 thanks for raising this! The only change in 0.22.0 was this one, which did not in any way change the way how state or context is managed. Some questions:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Ever since 0.22.0 I cannot boot the app, something has changed that breaks my app. Either I am doing something wrong and was just lucky this always worked? Or something bad happened.
My usage:
Since 0.22.0 this usage is no longer allowed, for some reason. Each component in the list within
GraphiQL.Toolbar
no longer has the required context provider; each and every one of them throws:Error: Tried to use <ComponentName> without the necessary context. Make sure to render the
EditorContextProvidercomponent higher up the tree.
The only packages from your mono repo I am using are these:
Any idea what is wrong here? Pinging @thomasheyenbrock since he is the one that authored 0.22.0 and 0.22.1 and @acao for merging.
Beta Was this translation helpful? Give feedback.
All reactions