Add operationName to ScriptContextData #2464
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
imolorhe
approved these changes
Mar 21, 2024
Merged
via the queue into
altair-graphql:master
with commit Mar 21, 2024
81414d4
7 of 11 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
#2463
Checks
yarn test-buildChanges proposed in this pull request:
This change adds
operationNamestring field to theScriptContextDataobject. The value is populated from the global state (state.query.selectedOperation).This value is then available through
altair.datahelper object in pre/post-request context.Docs have been updated to mention the newly available field.