fix(deps): update graphql-tools monorepo #545
Merged
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.
This PR contains the following updates:
^8.7.11
->^8.7.12
^8.3.14
->^8.4.0
Release Notes
ardatan/graphql-tools (@graphql-tools/delegate)
v8.7.12
Compare Source
Patch Changes
6df204d
: Remove graphql-executor to have smaller bundle size4914970
]ardatan/graphql-tools (@graphql-tools/schema)
v8.4.0
Compare Source
Minor Changes
4914970
:mergeSchemas
was skippingdefaultFieldResolver
anddefaultMergedResolver
by default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So newincludeDefaultMergedResolver
flag is introduced ingetResolversFromSchema
to put default "proxy" resolvers in the extracted resolver map formergeSchemas
.This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing
defaultMergedResolver
in the final merged schema which should come from the wrapped schema.Patch Changes
4914970
]Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.