-
-
Notifications
You must be signed in to change notification settings - Fork 3
chore(deps): update dependency graphql-tools to v9 #61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-graphql-tools-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+118
−9
Conversation
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
436904d to
2b2f765
Compare
2b2f765 to
6955e4c
Compare
6955e4c to
4aa0b3b
Compare
4aa0b3b to
9b5c685
Compare
9b5c685 to
c6bc751
Compare
c6bc751 to
6b3c188
Compare
6b3c188 to
25be13a
Compare
25be13a to
2c7c614
Compare
2c7c614 to
e435d7d
Compare
e435d7d to
17d48d2
Compare
17d48d2 to
331b63f
Compare
f8b1ea7 to
79db2fe
Compare
79db2fe to
1634c39
Compare
1634c39 to
59cf1fa
Compare
59cf1fa to
c72d685
Compare
c72d685 to
627387a
Compare
627387a to
95914a4
Compare
95914a4 to
c791e97
Compare
c791e97 to
7a2ec21
Compare
7a2ec21 to
73d61ee
Compare
dd4a9a3 to
cf4ee4a
Compare
cf4ee4a to
1c7f2e8
Compare
5d268c5 to
ba9db11
Compare
ba9db11 to
cc322b2
Compare
cc32a2c to
5923a40
Compare
5923a40 to
80c5469
Compare
d68d525 to
5f829c5
Compare
5f829c5 to
225208b
Compare
3a98f34 to
d9a5932
Compare
9aaeaa0 to
737b5b3
Compare
737b5b3 to
1407e8c
Compare
714e743 to
0a3a416
Compare
0a3a416 to
6379919
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:
4.0.4->9.0.23Release Notes
ardatan/graphql-tools (graphql-tools)
v9.0.23Compare Source
Patch Changes
v9.0.22Compare Source
Patch Changes
v9.0.21Compare Source
Patch Changes
v9.0.20Compare Source
Patch Changes
v9.0.19Compare Source
Patch Changes
v9.0.18Compare Source
Patch Changes
v9.0.17Compare Source
Patch Changes
v9.0.16Compare Source
Patch Changes
v9.0.15Compare Source
Patch Changes
v9.0.14Compare Source
Patch Changes
v9.0.13Compare Source
Patch Changes
v9.0.12Compare Source
Patch Changes
[
357b2ee]:v9.0.11Compare Source
Patch Changes
v9.0.10Compare Source
Patch Changes
v9.0.9Compare Source
Patch Changes
v9.0.8Compare Source
Patch Changes
v9.0.7Compare Source
Patch Changes
[
020b9e4]:v9.0.6Compare Source
Patch Changes
696a0d5Thanks @renovate! - dependencies updates:
@graphql-tools/schema@^10.0.10↗︎(from
^10.0.9, independencies)[
696a0d5]:v9.0.5Compare Source
Patch Changes
v9.0.4Compare Source
Patch Changes
v9.0.3Compare Source
Patch Changes
v9.0.2Compare Source
Patch Changes
v9.0.1Compare Source
Patch Changes
v9.0.0Compare Source
Major Changes
944a68e8Thanks @ardatan! - Drop Node 14 support. Require Node.js
>= 16Patch Changes
[
944a68e8]:v8.3.20Compare Source
Patch Changes
1c95368aThanks @ardatan! - Use ranged versions for dependencies
Updated dependencies
[
1c95368a]:v8.3.19Compare Source
Patch Changes
v8.3.18Compare Source
Patch Changes
v8.3.17Compare Source
Patch Changes
v8.3.16Compare Source
Patch Changes
v8.3.15Compare Source
Patch Changes
[
a4d36fcc]:v8.3.14Compare Source
Patch Changes
v8.3.13Compare Source
Patch Changes
v8.3.12Compare Source
Patch Changes
v8.3.11Compare Source
Patch Changes
v8.3.10Compare Source
Patch Changes
v8.3.9Compare Source
Patch Changes
v8.3.8Compare Source
Patch Changes
v8.3.7Compare Source
Patch Changes
v8.3.6Compare Source
Patch Changes
v8.3.5Compare Source
Patch Changes
v8.3.4Compare Source
Patch Changes
v8.3.3Compare Source
Patch Changes
[
2609d71f]:v8.3.2Compare Source
Patch Changes
1c95368aThanks @ardatan! - Use ranged versions for dependencies
Updated dependencies
[
1c95368a]:v8.3.1Compare Source
Patch Changes
v8.3.0Compare Source
Minor Changes
d76a299: Support TypeScript module resolution.Patch Changes
d76a299]v8.2.13Compare Source
Patch Changes
4914970]v8.2.12Compare Source
Patch Changes
041c5ba: Use caret range for the tslib dependency041c5ba]v8.2.11Compare Source
Patch Changes
v8.2.10Compare Source
Patch Changes
v8.2.9Compare Source
Patch Changes
v8.2.8Compare Source
Patch Changes
v8.2.7Compare Source
Patch Changes
v8.2.6Compare Source
Patch Changes
v8.2.5Compare Source
Patch Changes
v8.2.4Compare Source
Patch Changes
722abad]v8.2.3Compare Source
Patch Changes
v8.2.2Compare Source
Patch Changes
v8.2.1Compare Source
Patch Changes
4914970]v8.2.0Compare Source
Minor Changes
c5b0719: feat: GraphQL v16 supportPatch Changes
c5b0719]v8.1.0Compare Source
Minor Changes
b39588c: Deprecategraphql-toolswith a more clear message;This package has been deprecated and now it only exports makeExecutableSchema. It will no longer
receive updates. We strongly recommend you to migrate to scoped packages such as
@graphql-tools/schema, @graphql-tools/utils and etc. Check out https://www.graphql-tools.com to
learn which packages you should use instead!
v8.0.0Compare Source
Major Changes
7d3e300: BREAKING CHANGEmakeExecutableSchemafrom@graphql-tools/schema@graphql-tools/*) because this npm package will no longerget updated
Patch Changes
7d3e300]7d3e300]7d3e300]7d3e300]7d3e300]v7.0.5Compare Source
Patch Changes
52971f4: fix(graphql-tools): provide @apollo/client as an optional packageeae2879]v7.0.4Compare Source
Patch Changes
v7.0.3Compare Source
Patch Changes
2492665]2492665]2492665]v7.0.2Compare Source
Patch Changes
fb14cd2: Added export from new optimize packagefb14cd2]v7.0.1Compare Source
Patch Changes
294dedd]294dedd]2b6c813]8133a90]2b6c813]v7.0.0Compare Source
Major Changes
a925449: - Resolver validation options should now be set toerror,warnorignoreratherthan
trueorfalse. In previous versions, some of the validators caused errors to be thrown,while some issued warnings. This changes brings consistency to validator behavior.
allowResolversNotInSchemahas been renamed torequireResolversToMatchSchema, toharmonize the naming convention of all the validators. The default setting of
requireResolversToMatchSchemaiserror, matching the previous behavior.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)transformedSchemaparameters. As inv6, the
transformSchemais kicked off once to produce the non-executable version, and then, ifa wrapping schema is being generated, proxying resolvers are created with access to the
(non-executable) initial result. In v7, the individual
transformSchemamethods also get accessto the result of the first run, if necessary, they can create additional wrapping schema
proxying resolvers.
applySchemaTransformsparameters have been updated to match and support thetransformSchemaparameters above.
wrapSchemaandgenerateProxyingResolversnow only take a single options argument with namedproperties of type
SubschemaConfig. The previously possible shorthand version with firstargument consisting of a
GraphQLSchemaand second argument representing the transforms shouldbe reworked as a
SubschemaConfigobject.Similarly, the
ICreateProxyingResolverOptionsinterface that provides the options for thecreateProxyingResolverproperty ofSubschemaConfigoptions has been adjusted. Theschemaproperty previously could be set to a
GraphQLSchemaor aSubschemaConfigobject. Thisproperty has been removed in favor of a
subschemaConfigproperty that will always be aSubschemaConfigobject. Thetransformsproperty has been removed; transforms should beincluded within the
SubschemaConfigobject.`The format of the wrapping schema has solidified. All non-root fields are expected to use
identical resolvers, either
defaultMergedResolveror a custom equivalent, with root fieldsdoing the hard work of proxying. Support for custom merged resolvers throught
createMergedResolverhas been deprecated, as custom merging resolvers conflicts when usingstitching's type merging, where resolvers are expected to be identical across subschemas.
The
WrapFieldstransform'swrappingResolveroption has been removed, as this complicatesmultiple wrapping layers, as well as planned functionality to wrap subscription root fields in
potentially multiple layers, as the wrapping resolvers may be different in different layers.
Modifying resolvers can still be performed by use of an additional transform such as
TransformRootFieldsorTransformObjectFields.The
ExtendSchematransform has been removed, as it is conceptually simpler just to usestitchSchemaswith one subschema.The
ReplaceFieldsWithFragment,AddFragmentsByField,AddSelectionSetsByField, andAddMergedTypeSelectionSetstransforms has been removed, as they are superseded by theAddSelectionSetsandVisitSelectionSetstransforms. TheAddSelectionSetspurposely takesparsed SDL rather than strings, to nudge end users to parse these strings at build time (when
possible), rather than at runtime. Parsing of selection set strings can be performed using the
parseSelectionSetfunction from@graphql-tools/utils.stitchSchemas'smergeTypesoption is now true by default! This causes theonTypeConflictoption to be ignored by default. To use
onTypeConflictto select a specific type instead ofsimply merging, simply set
mergeTypesto false.schemasargument has been deprecated, usesubschemas,typeDefs, ortypes, depending onwhat you are stitching.
When using batch delegation in type merging, the
argsFromKeysfunction is now set only via theargsFromKeysproperty. Previously, ifargsFromKeyswas absent, it could be read fromargs.Support for fragment hints has been removed in favor of selection set hints.
stitchSchemasnow processes allGraphQLSchemaandSubschemaConfigsubschema input into newSubschemaobjects, handling schema config directives such aso@computedas well as generatingthe final transformed schema, stored as the
transformedSchemaproperty, if transforms areused. Signatures of the
onTypeConflict,fieldConfigMerger, andinputFieldConfigMergerhavebeen updated to include metadata related to the original and transformed subschemas. Note the
property name change for
onTypeConflictfromschematosubschema.graphql-js convention, i.e. these functions take three arguments,
args,context, andinfowith
parentavailable asthisrather than as the first argument.filterSchema'sfieldFilterwill now filter all fields across Object, Interface, and Inputtypes. For the previous Object-only behavior, switch to the
objectFieldFilteroption.fieldNodesutility functions have been removed.typeContainsSelectionSetfunction has been removed, andtypesContainSelectionSethasbeen moved to the
stitchpackage.Operationtype has been removed in favor ofOperationTypeNodefrom upstreamgraphql-js.
applySchemaTransforms/applyRequestTransforms/applyResultTransformshave beenremoved from the
utilspackage, as they are implemented elsewhere or no longer necessary.Patch Changes
a925449]v6.2.6Compare Source
Patch Changes
96a7555: Fix releaseLast PATCH release actually transitively updated graphql-tools and @graphql-tools/delegate to use
latest MAJOR version of dependencies.
Updated dependencies [
96a7555]v6.2.5Compare Source
Patch Changes
be1a157]v6.2.4Compare Source
Patch Changes
533d6d5: Bump all packages to allow adjustments32c3c4f]32c3c4f]32c3c4f]32c3c4f]32c3c4f]533d6d5]v6.2.3Compare Source
What’s Changed
🚀 Features
v6.2.2Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
v6.2.1Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
v6.2.0Compare Source
What’s Changed
🚀 Features
🐛 Bug Fixes
v6.1.0Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
v6.0.18Compare Source
✏️ Docs
🧰 Enhancements
parseto support converting comments into descriptions @dotansimha (#1900)v6.0.17Compare Source
What’s Changed
🚀 Features
🐛 Bug Fixes
instanceof Promiseto useis-promiselibrary @cajames (#1837)v6.0.16Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
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.
This PR was generated by Mend Renovate. View the repository job log.