chore(deps): update dependency @graphql-tools/schema to v10 #20
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}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #20 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 3
Lines 25 25
Branches 7 7
=========================================
Hits 25 25 ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
8d87d80 to
f0689f4
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
f0689f4 to
1fd1e48
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
1fd1e48 to
d14f0b9
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
d14f0b9 to
c8afb69
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
c8afb69 to
546ee57
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
546ee57 to
3393cdb
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
3393cdb to
2c2b03b
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
2c2b03b to
d784f55
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
9e96353 to
b48e0d6
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
b48e0d6 to
be6102b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
be6102b to
e5f5469
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
e5f5469 to
d6e6ba0
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
d6e6ba0 to
860c7aa
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
860c7aa to
cca5fe6
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
b07a67d to
4b4b5d3
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
4b4b5d3 to
fd2b64d
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
fd2b64d to
da2c133
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
c22c384 to
1e75f67
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
1e75f67 to
011f884
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
011f884 to
b666bb6
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
6aba9de to
cb1cfae
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
cb1cfae to
b77be38
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
3def757 to
6a42108
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
6a42108 to
c96cbd1
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
c96cbd1 to
49b807a
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
49b807a to
5c58167
Compare
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:
6.2.4->10.0.16Release Notes
ardatan/graphql-tools (@graphql-tools/schema)
v10.0.16Compare Source
Patch Changes
[
53bb601,53bb601]:v10.0.15Compare Source
Patch Changes
[
4912f19]:v10.0.14Compare Source
Patch Changes
[
2c70d27]:v10.0.13Compare Source
Patch Changes
[
6a8123b]:v10.0.12Compare Source
Patch Changes
020b9e4Thanks @ardatan! - `AbortSignal` in `GraphQLResolveInfo`, and
`AbortSignal` in `ExecutionRequest`
Updated dependencies
[
020b9e4]:v10.0.11Compare Source
Patch Changes
696a0d5Thanks @renovate! - dependencies updates:
@graphql-tools/merge@^9.0.11↗︎(from
^9.0.10, independencies)@graphql-tools/utils@^10.6.1↗︎(from
^10.6.0, independencies)[
696a0d5,1b24656]:v10.0.10Compare Source
Patch Changes
[
1e02935]:v10.0.9Compare Source
Patch Changes
[
414e404]:v10.0.8Compare Source
Patch Changes
[
dc5043b]:v10.0.7Compare Source
Patch Changes
[
cf2ce5e]:v10.0.6Compare Source
Patch Changes
0286437Thanks @ardatan! - Improve directive extraction
Updated dependencies
[
0286437]:v10.0.5Compare Source
Patch Changes
b8bf584Thanks @ardatan! - Introduce `getDirectiveExtensions` and refactor
directive handling in the extensions
Updated dependencies
[
b8bf584]:v10.0.4Compare Source
Patch Changes
#6194
7368829Thanks @ardatan! - Handle interface objects in a different way
Updated dependencies
[
7368829,e10c13a]:v10.0.3Compare Source
Patch Changes
83c0af0Thanks @enisdenjo! - dependencies updates:@graphql-tools/utils@^10.0.13↗︎ (from^10.0.10, independencies)83c0af0]:v10.0.2Compare Source
Patch Changes
a570a601Thanks @ardatan! - Add respectArrays flag to extensions merging
Updated dependencies
[
a570a601]:v10.0.1Compare Source
Patch Changes
e1fb8bb8Thanks @ardatan! - Merge directives in the extensions
Updated dependencies
[
e1fb8bb8]:v10.0.0Compare Source
Major Changes
944a68e8Thanks @ardatan! - Drop Node 14 support. Require Node.js>= 16Patch Changes
944a68e8,944a68e8]:v9.0.19Compare Source
Patch Changes
05c97eb8Thanks @ardatan! - dependencies updates:value-or-promise@^1.0.12↗︎ (from1.0.12, independencies)v9.0.18Compare Source
Patch Changes
1c95368aThanks @ardatan! - Use ranged versions for dependenciesUpdated dependencies [
1c95368a]:v9.0.17Compare Source
Patch Changes
04e3ecb9]:v9.0.16Compare Source
Patch Changes
b5c8f640]:v9.0.15Compare Source
Patch Changes
a94217e9,62d074be]:v9.0.14Compare Source
Patch Changes
8555c5c5]:v9.0.13Compare Source
Patch Changes
a4d36fccThanks @renovate! - dependencies updates:[email protected]↗︎ (from1.0.11, independencies)e3ec35ed]:v9.0.12Compare Source
Patch Changes
904fe770]:v9.0.11Compare Source
Patch Changes
[
13c24883]:v9.0.10Compare Source
Patch Changes
7411a5e7]:v9.0.9Compare Source
Patch Changes
c0639dd0]:v9.0.8Compare Source
Patch Changes
d83b1960]:v9.0.7Compare Source
Patch Changes
80836fa7,8f6d3efc,80836fa7,80836fa7,80836fa7]:v9.0.6Compare Source
Patch Changes
[
f7daf777]:v9.0.5Compare Source
Patch Changes
[
df5848b8,df5848b8,df5848b8]:v9.0.4Compare Source
Patch Changes
[
43c736bd]:v9.0.3Compare Source
Patch Changes
[
71cb4fae,403ed450]:v9.0.2Compare Source
Patch Changes
[
4fe3d9c0]:v9.0.1Compare Source
Patch Changes
05c97eb8Thanks @ardatan! - dependencies updates:
value-or-promise@^1.0.12↗︎ (from1.0.12, independencies)v9.0.0Compare Source
Major Changes
8cc8721fThanks @ardatan! - Thanks @mattkrick and @borisno2!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 abortedprematurely.
In previous versions, if
requireResolversToMatchSchemawas set toignore, although no errorwould 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]v8.3.1Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.3.0Compare Source
Minor Changes
149afdd: fix: getting ready for GraphQL v16Patch Changes
149afdd]v8.2.0Compare Source
Minor Changes
c5b0719: feat: GraphQL v16 supportPatch Changes
c5b0719]c5b0719]c5b0719]c5b0719]c5b0719]v8.1.2Compare Source
Patch Changes
e50852e: use version ranges instead of a fixed version for the graphql-tools package versionse50852e]v8.1.1Compare Source
Patch Changes
2c807dd]v8.1.0Compare Source
Minor Changes
67691b7: -schemaExtensionsoption has been added tomergeSchemas,makeExecutableSchemaandstitchSchemasconfigurationsBreaking Changes;
mergeSchemasandMergeSchemasConfigfrom@graphql-tools/mergeto@graphql-tools/schemapackage to prevent circular dependency between them.mergeSchemasAsynchas been removed.NamedDefinitionNode,resetComments,collectComment,pushCommentandprintCommentfrom
@graphql-tools/mergeto@graphql-tools/utils.Patch Changes
b968463]a5fb77a]9ede806]67691b7]v8.0.3Compare Source
Patch Changes
4992b47]v8.0.2Compare Source
Patch Changes
0483004]v8.0.1Compare Source
Patch Changes
b823dba]v8.0.0Compare Source
Major Changes
7d3e300: BREAKING CHANGE7d3e300: BREAKING CHANGEloggerandaddErrorLoggingToSchemaplugin system based library like Envelop
7d3e300: BREAKING CHANGEaddSchemaLevelResolverResolvers Composition
7d3e300: BREAKING CHANGEbuildSchemaFromTypeDefinitions, usebuildSchemafromgraphql-jsinsteadallowUndefinedResolveoption inmakeExecutableSchemabecause GraphQL Schema itselfdoes this checking
Patch Changes
7d3e300: enhance(schema): use merge package to handle typeDefs and resolvers mergingaf9a78d]9c26b84]7d3e300]7d3e300]dae6dc7]6877b91]c42e811]7d3e300]8c8d4fc]7d3e300]7d3e300]74581cf]c0ca319]982c8f5]7d3e300]a31f959]7d3e300]v7.1.5Compare Source
Patch Changes
22a9f3d: fix(deps): follow package conventions on when to pinv7.1.4Compare Source
Patch Changes
61da3e8: use value-or-promise to streamline working with sync values or async promisesv7.1.3Compare Source
Patch Changes
c8e26b8: fix(schema): ignore resolvers if they are not in schemav7.1.2Compare Source
Patch Changes
21da690: fix release21da690]v7.1.0Compare Source
Minor Changes
4f5a4ef: enhance(schema): add some options to improve schema creation performancePatch Changes
65ed780: enhance(schema): do not visit resolvers if no validation is selectedb79e3a6: enhance(schema): do not visit abstract types if requireResolversForResolveType notpresent
4f5a4ef]v7.0.0Compare Source
Major Changes
be1a157: ## Breaking Changes:Schema Generation and Decoration API (
@graphql-tools/schema)Resolver validation options should now be set to
error,warnorignorerather thantrueor
false. In previous versions, some of the validators caused errors to be thrown, while someissued warnings. This changes brings consistency to validator behavior.
The
allowResolversNotInSchemahas been renamed torequireResolversToMatchSchema, toharmonize the naming convention of all the validators. The default setting of
requireResolversToMatchSchemaiserror, matching the previous behavior.Schema Delegation (
delegateToSchema&@graphql-tools/delegate)The
delegateToSchemareturn value has matured and been formalized as anExternalObject, inwhich all errors are integrated into the GraphQL response, preserving their initial path. Those
advanced users accessing the result directly will note the change in error handling. This also
allows for the deprecation of unnecessary helper functions including
slicedError,getErrors,getErrorsByPathSegmentfunctions. Only external errors with missing or invalid paths muststill be preserved by annotating the remote object with special properties. The new
getUnpathedErrorsfunction is therefore necessary for retrieving only these errors. Note alsothe new
annotateExternalObjectandmergeExternalObjectsfunctions, as well as the renamingof
handleResulttoresolveExternalValue.Transform types and the
applySchemaTransformsare now relocated to thedelegatepackage;applyRequestTransforms/applyResultTransformsfunctions have been deprecated, however, asthis functionality has been replaced since v6 by the
Transformerabstraction.The
transformRequest/transformResultmethods are now provided additionaldelegationContextand
transformationContextarguments -- these were introduced in v6, but previously optional.The
transformSchemamethod may wish to create additional delegating resolvers and so it is nowprovided the
subschemaConfigand final (non-executable)transformedSchemaConfiguration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.