always use the latest header values for introspection #2451
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2442
After introducing the schema context, we might dispatch introspection queries after the initial one that don't use the latest header values, but the initial ones. This PR fixes this:
EditorContextProvider
and also expose them on the context value. The editor hooks don't need to do this logic anymore and can just consume the initial value from the context.useSynchronizeValue
) have been moved to theEditorContextProvider
, that way we only need to pass thedefaultQuery
,query
,variables
, andheaders
prop to the context provider and not also the editor hooks.SchemaContextProvider
to make sure that we use the latest header values when initializing an introspection request.