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

Name operations #1700

Merged
merged 2 commits into from Jun 28, 2020
Merged

Name operations #1700

merged 2 commits into from Jun 28, 2020

Conversation

yaacovCR
Copy link
Collaborator

@yaacovCR yaacovCR commented Jun 28, 2020

alternative to #1651

allows specification of operation name when delegating without a default. no need to allow a function as discussed there, as caller will always have access to the existing operation name under the info argument.

you can use the subschema createProxyingResolver option to enable setting the operation for delegation to a subschema when wrapping or stitching subschemas.

you can also just set the operation name in a transform (now that the second argument of a transformRequest function is the delegationContext)

you can also set the operation name within the executor function, now that info argument is passed there.

@theguild-bot
Copy link
Collaborator

theguild-bot commented Jun 28, 2020

The latest changes of this PR are available as alpha in npm: 6.0.12-alpha-dbe38eb.0

Quickly update your package.json by running:

npx match-version @graphql-tools 6.0.12-alpha-dbe38eb.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants