update @graphql-tools/schema to 8.5.1 #209
Closed
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Branch automerge failureThis PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead.
|
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
fd70f85 to
188c4e3
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
188c4e3 to
2c2aa97
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
2c2aa97 to
b6e915b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
b6e915b to
20e1826
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
20e1826 to
d73ac26
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/graphql-tools-monorepo
branch
from
d73ac26 to
bf4da41
Compare
renovate
bot
changed the title
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.
This PR contains the following updates:
^8.3.1->8.5.1Release Notes
ardatan/graphql-tools
v8.5.1Compare Source
Patch Changes
2a3b45e]v8.5.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
a0abbbc]d76a299]v8.4.0Compare Source
Minor Changes
4914970:mergeSchemaswas skippingdefaultFieldResolveranddefaultMergedResolverby 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 newincludeDefaultMergedResolverflag is introduced ingetResolversFromSchemato 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
defaultMergedResolverin the final merged schema which should come from the wrapped schema.Patch Changes
4914970]v8.3.14Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.3.13Compare Source
Patch Changes
da7ad43]v8.3.12Compare Source
Patch Changes
c0762ee]v8.3.11Compare Source
Patch Changes
0fc510c]v8.3.10Compare Source
Patch Changes
31a33e2]v8.3.9Compare Source
Patch Changes
cb23887]v8.3.8Compare Source
Patch Changes
0bbb176]v8.3.7Compare Source
Patch Changes
904c084]v8.3.6Compare Source
Patch Changes
722abad: FixaddResolversToSchemabug where type or field processing would be aborted prematurely.In previous versions, if
requireResolversToMatchSchemawas set toignore, although no error would be thrown for an unexpected resolver type, type processing would still be aborted early. This fix changes the behavior to correctly continue resolver type processing with the next provided type.In previous versions, if a resolver field began with double underscores, it would correctly be used for legacy behavior to directly set a type property, but field processing would be aborted early. This fix changes the behavior to correctly continue type processing with the next field.
v8.3.5Compare Source
Patch Changes
be2c02d]v8.3.4Compare Source
Patch Changes
d36d530]v8.3.3Compare Source
Patch Changes
0c0c685: fix - align versions0c0c685]v8.3.2Compare Source
Patch Changes
1834136: feat(visitResult): ignore if field not present in visited object1834136]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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.