-
Notifications
You must be signed in to change notification settings - Fork 174
Update dependency graphql-tools to v9 (master) #1444
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/master-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.
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
d0d0b69
to
473ce63
Compare
473ce63
to
6a905a9
Compare
6a905a9
to
73a6691
Compare
73a6691
to
e619399
Compare
e619399
to
8cb0b91
Compare
8cb0b91
to
665d62b
Compare
665d62b
to
28030b0
Compare
28030b0
to
9b199ed
Compare
9b199ed
to
27bccee
Compare
27bccee
to
8bb9ef7
Compare
8bb9ef7
to
ba3e26a
Compare
5697772
to
6721a5d
Compare
6721a5d
to
815d4d8
Compare
815d4d8
to
7cad7e1
Compare
7cad7e1
to
2c8cf8d
Compare
2c8cf8d
to
4259fe8
Compare
4259fe8
to
6819224
Compare
6819224
to
bbe3ef5
Compare
bbe3ef5
to
259d6e4
Compare
c71a015
to
cb94806
Compare
cb94806
to
5309b21
Compare
a35b22a
to
ec0aee4
Compare
ec0aee4
to
4232e0c
Compare
4232e0c
to
6d75ec1
Compare
6d75ec1
to
c65b955
Compare
c65b955
to
1a38b44
Compare
aba74d1
to
421d273
Compare
421d273
to
39d8717
Compare
39d8717
to
c0ca11b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
5.0.0
->9.0.18
Release Notes
ardatan/graphql-tools (graphql-tools)
v9.0.18
Compare Source
Patch Changes
v9.0.17
Compare Source
Patch Changes
v9.0.16
Compare Source
Patch Changes
v9.0.15
Compare Source
Patch Changes
v9.0.14
Compare Source
Patch Changes
v9.0.13
Compare Source
Patch Changes
v9.0.12
Compare Source
Patch Changes
[
357b2ee
]:v9.0.11
Compare Source
Patch Changes
v9.0.10
Compare Source
Patch Changes
v9.0.9
Compare Source
Patch Changes
v9.0.8
Compare Source
Patch Changes
v9.0.7
Compare Source
Patch Changes
[
020b9e4
]:v9.0.6
Compare Source
Patch Changes
696a0d5
Thanks @renovate! - dependencies updates:
@graphql-tools/schema@^10.0.10
↗︎(from
^10.0.9
, independencies
)[
696a0d5
]:v9.0.5
Compare Source
Patch Changes
v9.0.4
Compare Source
Patch Changes
v9.0.3
Compare Source
Patch Changes
v9.0.2
Compare Source
Patch Changes
v9.0.1
Compare Source
Patch Changes
v9.0.0
Compare Source
Major Changes
944a68e8
Thanks @ardatan! - Drop Node 14 support. Require Node.js
>= 16
Patch Changes
[
944a68e8
]:v8.3.20
Compare Source
Patch Changes
1c95368a
Thanks @ardatan! - Use ranged versions for dependencies
Updated dependencies
[
1c95368a
]:v8.3.19
Compare Source
Patch Changes
v8.3.18
Compare Source
Patch Changes
v8.3.17
Compare Source
Patch Changes
v8.3.16
Compare Source
Patch Changes
v8.3.15
Compare Source
Patch Changes
[
a4d36fcc
]:v8.3.14
Compare Source
Patch Changes
v8.3.13
Compare Source
Patch Changes
v8.3.12
Compare Source
Patch Changes
v8.3.11
Compare Source
Patch Changes
v8.3.10
Compare Source
Patch Changes
v8.3.9
Compare Source
Patch Changes
v8.3.8
Compare Source
Patch Changes
v8.3.7
Compare Source
Patch Changes
v8.3.6
Compare Source
Patch Changes
v8.3.5
Compare Source
Patch Changes
v8.3.4
Compare Source
Patch Changes
v8.3.3
Compare Source
Patch Changes
[
2609d71f
]:v8.3.2
Compare Source
Patch Changes
1c95368a
Thanks @ardatan! - Use ranged versions for dependencies
Updated dependencies
[
1c95368a
]:v8.3.1
Compare Source
Patch Changes
v8.3.0
Compare Source
Minor Changes
d76a299
: Support TypeScript module resolution.Patch Changes
d76a299
]v8.2.13
Compare Source
Patch Changes
4914970
]v8.2.12
Compare Source
Patch Changes
041c5ba
: Use caret range for the tslib dependency041c5ba
]v8.2.11
Compare Source
Patch Changes
v8.2.10
Compare Source
Patch Changes
v8.2.9
Compare Source
Patch Changes
v8.2.8
Compare Source
Patch Changes
v8.2.7
Compare Source
Patch Changes
v8.2.6
Compare Source
Patch Changes
v8.2.5
Compare Source
Patch Changes
v8.2.4
Compare Source
Patch Changes
722abad
]v8.2.3
Compare Source
Patch Changes
v8.2.2
Compare Source
Patch Changes
v8.2.1
Compare Source
Patch Changes
4914970
]v8.2.0
Compare Source
Minor Changes
c5b0719
: feat: GraphQL v16 supportPatch Changes
c5b0719
]v8.1.0
Compare Source
Minor Changes
b39588c
: Deprecategraphql-tools
with 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.0
Compare Source
Major Changes
7d3e300
: BREAKING CHANGEmakeExecutableSchema
from@graphql-tools/schema
@graphql-tools/*
) because this npm package will no longerget updated
Patch Changes
7d3e300
]7d3e300
]7d3e300
]7d3e300
]7d3e300
]v7.0.5
Compare Source
Patch Changes
52971f4
: fix(graphql-tools): provide @apollo/client as an optional packageeae2879
]v7.0.4
Compare Source
Patch Changes
v7.0.3
Compare Source
Patch Changes
2492665
]2492665
]2492665
]v7.0.2
Compare Source
Patch Changes
fb14cd2
: Added export from new optimize packagefb14cd2
]v7.0.1
Compare Source
Patch Changes
294dedd
]294dedd
]2b6c813
]8133a90
]2b6c813
]v7.0.0
Compare Source
Major Changes
a925449
: - Resolver validation options should now be set toerror
,warn
orignore
ratherthan
true
orfalse
. In previous versions, some of the validators caused errors to be thrown,while some issued warnings. This changes brings consistency to validator behavior.
allowResolversNotInSchema
has been renamed torequireResolversToMatchSchema
, toharmonize the naming convention of all the validators. The default setting of
requireResolversToMatchSchema
iserror
, matching the previous behavior.The
delegateToSchema
return 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
,getErrorsByPathSegment
functions. Only external errors with missing or invalid paths muststill be preserved by annotating the remote object with special properties. The new
getUnpathedErrors
function is therefore necessary for retrieving only these errors. Note alsothe new
annotateExternalObject
andmergeExternalObjects
functions, as well as the renamingof
handleResult
toresolveExternalValue
.Transform types and the
applySchemaTransforms
are now relocated to thedelegate
package;applyRequestTransforms
/applyResultTransforms
functions have been deprecated, however, asthis functionality has been replaced since v6 by the
Transformer
abstraction.The
transformRequest
/transformResult
methods are now provided additionaldelegationContext
and
transformationContext
arguments -- these were introduced in v6, but previously optional.The
transformSchema
method may wish to create additional delegating resolvers and so it is nowprovided the
subschemaConfig
and final (non-executable)transformedSchema
parameters. As inv6, the
transformSchema
is 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
transformSchema
methods also get accessto the result of the first run, if necessary, they can create additional wrapping schema
proxying resolvers.
applySchemaTransforms
parameters have been updated to match and support thetransformSchema
parameters above.
wrapSchema
andgenerateProxyingResolvers
now only take a single options argument with namedproperties of type
SubschemaConfig
. The previously possible shorthand version with firstargument consisting of a
GraphQLSchema
and second argument representing the transforms shouldbe reworked as a
SubschemaConfig
object.Similarly, the
ICreateProxyingResolverOptions
interface that provides the options for thecreateProxyingResolver
property ofSubschemaConfig
options has been adjusted. Theschema
property previously could be set to a
GraphQLSchema
or aSubschemaConfig
object. Thisproperty has been removed in favor of a
subschemaConfig
property that will always be aSubschemaConfig
object. Thetransforms
property has been removed; transforms should beincluded within the
SubschemaConfig
object.`The format of the wrapping schema has solidified. All non-root fields are expected to use
identical resolvers, either
defaultMergedResolver
or a custom equivalent, with root fieldsdoing the hard work of proxying. Support for custom merged resolvers throught
createMergedResolver
has been deprecated, as custom merging resolvers conflicts when usingstitching's type merging, where resolvers are expected to be identical across subschemas.
The
WrapFields
transform'swrappingResolver
option 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
TransformRootFields
orTransformObjectFields
.The
ExtendSchema
transform has been removed, as it is conceptually simpler just to usestitchSchemas
with one subschema.The
ReplaceFieldsWithFragment
,AddFragmentsByField
,AddSelectionSetsByField
, andAddMergedTypeSelectionSets
transforms has been removed, as they are superseded by theAddSelectionSets
andVisitSelectionSets
transforms. TheAddSelectionSets
purposely 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
parseSelectionSet
function from@graphql-tools/utils
.stitchSchemas
'smergeTypes
option is now true by default! This causes theonTypeConflict
option to be ignored by default. To use
onTypeConflict
to select a specific type instead ofsimply merging, simply set
mergeTypes
to false.schemas
argument has been deprecated, usesubschemas
,typeDefs
, ortypes
, depending onwhat you are stitching.
When using batch delegation in type merging, the
argsFromKeys
function is now set only via theargsFromKeys
property. Previously, ifargsFromKeys
was absent, it could be read fromargs
.Support for fragment hints has been removed in favor of selection set hints.
stitchSchemas
now processes allGraphQLSchema
andSubschemaConfig
subschema input into newSubschema
objects, handling schema config directives such aso@computed
as well as generatingthe final transformed schema, stored as the
transformedSchema
property, if transforms areused. Signatures of the
onTypeConflict
,fieldConfigMerger
, andinputFieldConfigMerger
havebeen updated to include metadata related to the original and transformed subschemas. Note the
property name change for
onTypeConflict
fromschema
tosubschema
.graphql-js convention, i.e. these functions take three arguments,
args
,context
, andinfo
with
parent
available asthis
rather than as the first argument.filterSchema
'sfieldFilter
will now filter all fields across Object, Interface, and Inputtypes. For the previous Object-only behavior, switch to the
objectFieldFilter
option.fieldNodes
utility functions have been removed.typeContainsSelectionSet
function has been removed, andtypesContainSelectionSet
hasbeen moved to the
stitch
package.Operation
type has been removed in favor ofOperationTypeNode
from upstreamgraphql-js.
applySchemaTransforms
/applyRequestTransforms
/applyResultTransforms
have beenremoved from the
utils
package, as they are implemented elsewhere or no longer necessary.Patch Changes
a925449
]v6.2.6
Compare 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.5
Compare Source
Patch Changes
be1a157
]v6.2.4
Compare Source
Patch Changes
533d6d5
: Bump all packages to allow adjustments32c3c4f
]32c3c4f
]32c3c4f
]32c3c4f
]32c3c4f
]533d6d5
]v6.2.3
Compare Source
What’s Changed
🚀 Features
v6.2.2
Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
v6.2.1
Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
v6.2.0
Compare Source
What’s Changed
🚀 Features
🐛 Bug Fixes
v6.1.0
Compare Source
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
v6.0.18
Compare Source
✏️ Docs
🧰 Enhancements
parse
to support converting comments into descriptions @dotansimha (#1900)v6.0.17
Compare Source
What’s Changed
🚀 Features
🐛 Bug Fixes
instanceof Promise
to useis-promise
library @cajames (#1837)v6.0.16
Compare Source
What’s Changed
🧰 Enhancements
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 is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.