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
chore(deps): update dependency graphql-tools to v8 #150
Merged
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
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
4 times, most recently
from
June 3, 2020 15:56
c586466
to
8097bc3
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
June 8, 2020 17:00
4e54e2b
to
941a438
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
June 15, 2020 16:11
941a438
to
e567850
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
June 25, 2020 22:52
b987b1b
to
d6f2b1d
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
July 9, 2020 02:38
46bf213
to
63d1cca
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
July 16, 2020 12:49
915b46a
to
5a8561d
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
July 28, 2020 17:35
decb8d7
to
36e137d
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
3 times, most recently
from
August 5, 2020 08:59
de76989
to
a9c5029
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
4 times, most recently
from
August 13, 2020 00:37
a28c51c
to
e2826fb
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
3 times, most recently
from
August 26, 2020 09:47
ec0a153
to
1354f68
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
September 4, 2020 16:07
9a18fe3
to
44de630
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
September 19, 2020 08:19
1d33ae4
to
486657e
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
September 30, 2020 07:28
486657e
to
6fa2d78
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
2 times, most recently
from
May 12, 2021 22:00
796b55f
to
5e85c1a
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
3 times, most recently
from
May 29, 2021 02:30
e98d115
to
c04070e
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
3 times, most recently
from
June 9, 2021 00:57
09b0936
to
d034c22
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
July 28, 2021 11:25
d034c22
to
fd1a38f
Compare
renovate
bot
changed the title
chore(deps): update dependency graphql-tools to v7
chore(deps): update dependency graphql-tools to v8
Jul 28, 2021
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
August 4, 2021 15:03
fd1a38f
to
506828a
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
October 18, 2021 20:05
506828a
to
2217d24
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
14 times, most recently
from
March 26, 2022 19:08
c73abfc
to
1f81129
Compare
renovate
bot
force-pushed
the
renovate/major-graphql-tools-monorepo
branch
from
March 26, 2022 19:10
1f81129
to
acd35a7
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:
5.0.0
->8.2.3
Release Notes
ardatan/graphql-tools
v8.2.3
Compare Source
Patch Changes
v8.2.2
Compare Source
Patch Changes
v8.2.1
Compare Source
Patch Changes
0c0c685
: fix - align versions0c0c685
]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 longer get updatedPatch 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
rather thantrue
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
, to harmonize the naming convention of all the validators. The default setting ofrequireResolversToMatchSchema
iserror
, matching the previous behavior.The
delegateToSchema
return value has matured and been formalized as anExternalObject
, in which 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 includingslicedError
,getErrors
,getErrorsByPathSegment
functions. Only external errors with missing or invalid paths must still be preserved by annotating the remote object with special properties. The newgetUnpathedErrors
function is therefore necessary for retrieving only these errors. Note also the newannotateExternalObject
andmergeExternalObjects
functions, as well as the renaming ofhandleResult
toresolveExternalValue
.Transform types and the
applySchemaTransforms
are now relocated to thedelegate
package;applyRequestTransforms
/applyResultTransforms
functions have been deprecated, however, as this functionality has been replaced since v6 by theTransformer
abstraction.The
transformRequest
/transformResult
methods are now provided additionaldelegationContext
andtransformationContext
arguments -- these were introduced in v6, but previously optional.The
transformSchema
method may wish to create additional delegating resolvers and so it is now provided thesubschemaConfig
and final (non-executable)transformedSchema
parameters. As in v6, thetransformSchema
is kicked off once to produce the non-executable version, and then, if a wrapping schema is being generated, proxying resolvers are created with access to the (non-executable) initial result. In v7, the individualtransformSchema
methods also get access to 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 named properties of typeSubschemaConfig
. The previously possible shorthand version with first argument consisting of aGraphQLSchema
and second argument representing the transforms should be reworked as aSubschemaConfig
object.Similarly, the
ICreateProxyingResolverOptions
interface that provides the options for thecreateProxyingResolver
property ofSubschemaConfig
options has been adjusted. Theschema
property previously could be set to aGraphQLSchema
or aSubschemaConfig
object. This property has been removed in favor of asubschemaConfig
property that will always be aSubschemaConfig
object. Thetransforms
property has been removed; transforms should be included within theSubschemaConfig
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 fields doing the hard work of proxying. Support for custom merged resolvers throughtcreateMergedResolver
has been deprecated, as custom merging resolvers conflicts when using stitching's type merging, where resolvers are expected to be identical across subschemas.The
WrapFields
transform'swrappingResolver
option has been removed, as this complicates multiple 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 asTransformRootFields
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 takes parsed 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 theparseSelectionSet
function from@graphql-tools/utils
.stitchSchemas
'smergeTypes
option is now true by default! This causes theonTypeConflict
option to be ignored by default. To useonTypeConflict
to select a specific type instead of simply merging, simply setmergeTypes
to false.schemas
argument has been deprecated, usesubschemas
,typeDefs
, ortypes
, depending on what 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 generating the final transformed schema, stored as thetransformedSchema
property, if transforms are used. Signatures of theonTypeConflict
,fieldConfigMerger
, andinputFieldConfigMerger
have been updated to include metadata related to the original and transformed subschemas. Note the property name change foronTypeConflict
fromschema
tosubschema
.args
,context
, andinfo
withparent
available asthis
rather than as the first argument.filterSchema
'sfieldFilter
will now filter all fields across Object, Interface, and Input types. For the previous Object-only behavior, switch to theobjectFieldFilter
option.fieldNodes
utility functions have been removed.typeContainsSelectionSet
function has been removed, andtypesContainSelectionSet
has been moved to thestitch
package.Operation
type has been removed in favor ofOperationTypeNode
from upstream graphql-js.applySchemaTransforms
/applyRequestTransforms
/applyResultTransforms
have been removed from theutils
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
🐛 Bug Fixes
v6.0.15
Compare Source
What’s Changed
🚀 Features
graphql-tag/loader
(more customizable, much smaller output, bundle size improvements) @kamilkisiela (#1815)🧰 Enhancements
🐛 Bug Fixes
v6.0.14
Compare Source
What’s Changed
🚀 Features
🧰 Enhancements
🐛 Bug Fixes
v6.0.13
Compare Source
What’s Changed
🚀 Features
🧰 Enhancements
🐛 Bug Fixes
v6.0.12
Compare Source
What’s Changed
🐛 Bug Fixes
v6.0.11
Compare Source
What’s Changed
🚀 Features
🐛 Bug Fixes
mergeDirectives
@rufman (#1671)v6.0.10
Compare Source
What’s Changed
🚀 Features
🐛 Bug Fixes
v6.0.9
Compare Source
v6.0.8
Compare Source
UrlLoader
.v6.0.7
Compare Source
skipGraphQLImport
's behaviorv6.0.6
Compare Source
generateProxyingResolvers
to public API for v6.0.0 (#1570) - Thanks @marcammann !v6.0.5
Compare Source
v6.0.4
Compare Source
v6.0.3
Compare Source
@graphql-tools/url-loader
to fetch queries using HTTP GET Query GraphQL backend with HTTP GET ardatan/graphql-mesh#478v6.0.2
Compare Source
@graphql-tools/url-loader
andintrospectSchema
https://github.com/dotansimha/graphql-code-generator/issues/4098loadFiles
path resolving issue in@graphql-tools/load-files
(#1542)@graphql-tools/url-loader
v6.0.1
Compare Source
graphql-tools
npm package (#1524)v6.0.0
Compare Source
A huge v6 release with a new monorepo structure!
You can learn more about changes by checking out our:
New Monorepo Structure
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by WhiteSource Renovate. View repository job log here.