Update dependency @graphql-tools/utils to v11#1036
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
e1af095 to
591e529
Compare
591e529 to
30f561c
Compare
30f561c to
da72f93
Compare
ef76af5 to
fe16fcf
Compare
fe16fcf to
33bf6e5
Compare
33bf6e5 to
354ac0f
Compare
This file contains hidden or 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
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:
10.11.0→11.1.1Release Notes
ardatan/graphql-tools (@graphql-tools/utils)
v11.1.1Compare Source
Patch Changes
#8256
981d461Thanks @twavv! - Fix
mergeDeepreturningundefinedinstead of{}when merging two or more empty objects.
Previously the output accumulator was only initialized inside the per-key loop, so merging sources
with no own keys (e.g.
mergeDeep([{}, {}])) left itundefined. This silently droppedempty-object values during nested merges (
{ data: {} }became{ data: undefined }), whichcould surface as "Cannot return null for non-nullable field" errors when stitching schemas. The
accumulator is now initialized as soon as an object source is encountered.
v11.1.0Compare Source
Minor Changes
a4b7dceThanks @enisdenjo! - Deep merge and preserve non-enumerable
symbols
v11.0.1Compare Source
Patch Changes
ae36a0eThanks @mattkrick! - Handle enum values correctly if they are
arguments of directives defined in the extensions
v11.0.0Compare Source
Major Changes
#7685
6f3776cThanks @ardatan! - Support "federation/subgraph style" schemas in
astFromSchemaandprintSchemaWithDirectivesIf a
GraphQLSchemadoesn't have any defined operation types, we should print the schemadefinition as an extension rather than omitting it entirely. They are not a valid schema on their
own, but they are valid subgraph schemas in a federation setup, and it is possible to build such
schemas with
assumeValidoptions.POTENTIAL BREAKING CHANGE: This can be a breaking change because now the schema above will be
printed as the input, previously
extend schemawas converted toschema {}.Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.