graphql.github.io
graphql.github.io copied to clipboard
Update dependency @graphql-tools/schema to v8.5.1
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
@graphql-tools/schema | 8.3.1 -> 8.5.1 |
Release Notes
ardatan/graphql-tools
v8.5.1
Patch Changes
- Updated dependencies [
2a3b45e
]
v8.5.0
Minor Changes
-
d76a299
: Support TypeScript module resolution.
Patch Changes
v8.4.0
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
- Updated dependencies [
4914970
]
v8.3.14
Patch Changes
v8.3.13
Patch Changes
- Updated dependencies [
da7ad43
]
v8.3.12
Patch Changes
- Updated dependencies [
c0762ee
]
v8.3.11
Patch Changes
- Updated dependencies [
0fc510c
]
v8.3.10
Patch Changes
- Updated dependencies [
31a33e2
]
v8.3.9
Patch Changes
- Updated dependencies [
cb23887
]
v8.3.8
Patch Changes
- Updated dependencies [
0bbb176
]
v8.3.7
Patch Changes
- Updated dependencies [
904c084
]
v8.3.6
Patch Changes
-
722abad
: FixaddResolversToSchema
bug where type or field processing would be aborted prematurely.In previous versions, if
requireResolversToMatchSchema
was 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.5
Patch Changes
- Updated dependencies [
be2c02d
]
v8.3.4
Patch Changes
- Updated dependencies [
d36d530
]
v8.3.3
Patch Changes
v8.3.2
Patch Changes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
- [ ] If you want to rebase/retry this PR, click this checkbox.
This PR has been generated by Mend Renovate. View repository job log here.