WhatsApp-Clone-Server
WhatsApp-Clone-Server copied to clipboard
Update dependency graphql-tools to v9 (master)
This PR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
graphql-tools (source) | 5.0.0 -> 9.0.1 |
Release Notes
ardatan/graphql-tools (graphql-tools)
v9.0.1
Patch Changes
-
#5913
83c0af0
Thanks @enisdenjo! - dependencies updates:- Updated dependency
@graphql-tools/schema@^10.0.2
↗︎ (from^10.0.0
, independencies
)
- Updated dependency
- Updated dependencies [
83c0af0
]:
v9.0.0
Major Changes
Patch Changes
- Updated dependencies [
944a68e8
]:
v8.3.20
Patch Changes
v8.3.19
Patch Changes
- Updated dependencies []:
v8.3.18
Patch Changes
- Updated dependencies []:
v8.3.17
Patch Changes
- Updated dependencies []:
v8.3.16
Patch Changes
- Updated dependencies []:
v8.3.15
Patch Changes
- Updated dependencies [
a4d36fcc
]:
v8.3.14
Patch Changes
- Updated dependencies []:
v8.3.13
Patch Changes
- Updated dependencies []:
v8.3.12
Patch Changes
- Updated dependencies []:
v8.3.11
Patch Changes
- Updated dependencies []:
v8.3.10
Patch Changes
- Updated dependencies []:
v8.3.9
Patch Changes
- Updated dependencies []:
v8.3.8
Patch Changes
- Updated dependencies []:
v8.3.7
Patch Changes
- Updated dependencies []:
v8.3.6
Patch Changes
- Updated dependencies []:
v8.3.5
Patch Changes
- Updated dependencies []:
v8.3.4
Patch Changes
- Updated dependencies []:
v8.3.3
Patch Changes
- Updated dependencies [
2609d71f
]:
v8.3.2
Patch Changes
v8.3.1
Patch Changes
- Updated dependencies []:
v8.3.0
Minor Changes
-
d76a299
: Support TypeScript module resolution.
Patch Changes
- Updated dependencies [
d76a299
]
v8.2.13
Patch Changes
- Updated dependencies [
4914970
]
v8.2.12
Patch Changes
v8.2.11
Patch Changes
v8.2.10
Patch Changes
v8.2.9
Patch Changes
v8.2.8
Patch Changes
v8.2.7
Patch Changes
v8.2.6
Patch Changes
v8.2.5
Patch Changes
v8.2.4
Patch Changes
- Updated dependencies [
722abad
]
v8.2.3
Patch Changes
v8.2.2
Patch Changes
v8.2.1
Patch Changes
- Updated dependencies [
4914970
]
v8.2.0
Minor Changes
-
c5b0719
: feat: GraphQL v16 support
Patch Changes
- Updated dependencies [
c5b0719
]
v8.1.0
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
Major Changes
-
7d3e300
: BREAKING CHANGE- Now it only exports
makeExecutableSchema
from@graphql-tools/schema
- Please migrate to scoped packages(
@graphql-tools/*
) because this npm package will no longer get updated
- Now it only exports
Patch Changes
- Updated dependencies [
7d3e300
] - Updated dependencies [
7d3e300
] - Updated dependencies [
7d3e300
] - Updated dependencies [
7d3e300
] - Updated dependencies [
7d3e300
]
v7.0.5
Patch Changes
-
52971f4
: fix(graphql-tools): provide @apollo/client as an optional package - Updated dependencies [
eae2879
]
v7.0.4
Patch Changes
- Revert mock package to v7 to avoid breaking changes
v7.0.3
Patch Changes
v7.0.2
Patch Changes
v7.0.1
Patch Changes
- Updated dependencies [
294dedd
] - Updated dependencies [
294dedd
] - Updated dependencies [
2b6c813
] - Updated dependencies [
8133a90
] - Updated dependencies [
2b6c813
]
v7.0.0
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.- The
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
.
- Mocks returning objects with fields set as functions are now operating according to upstream graphql-js convention, i.e. these functions take three arguments,
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. - Unused
fieldNodes
utility functions have been removed. - Unused
typeContainsSelectionSet
function has been removed, andtypesContainSelectionSet
has been moved to thestitch
package. - Unnecessary
Operation
type has been removed in favor ofOperationTypeNode
from upstream graphql-js. - As above,
applySchemaTransforms
/applyRequestTransforms
/applyResultTransforms
have been removed from theutils
package, as they are implemented elsewhere or no longer necessary.
- The
Patch Changes
- Updated dependencies [
a925449
]
v6.2.6
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
Patch Changes
- Updated dependencies [
be1a157
]- @graphql-tools/batch-execute@7.0.0
- @graphql-tools/delegate@7.0.0
- @graphql-tools/mock@7.0.0
- @graphql-tools/schema@7.0.0
- @graphql-tools/stitch@7.0.0
- @graphql-tools/utils@7.0.0
- @graphql-tools/wrap@7.0.0
- @graphql-tools/links@6.2.5
- @graphql-tools/merge@6.2.5
- @graphql-tools/batch-delegate@6.2.5
- @graphql-tools/url-loader@6.3.1
- @graphql-tools/graphql-tag-pluck@6.2.6
- @graphql-tools/load@6.2.5
- @graphql-tools/code-file-loader@6.2.5
- @graphql-tools/git-loader@6.2.5
- @graphql-tools/github-loader@6.2.5
- @graphql-tools/graphql-file-loader@6.2.5
- @graphql-tools/json-file-loader@6.2.5
- @graphql-tools/module-loader@6.2.5
- @graphql-tools/relay-operation-optimizer@6.2.5
- @graphql-tools/resolvers-composition@6.2.5
v6.2.4
Patch Changes
-
533d6d5
: Bump all packages to allow adjustments - Updated dependencies [
32c3c4f
] - Updated dependencies [
32c3c4f
] - Updated dependencies [
32c3c4f
] - Updated dependencies [
32c3c4f
] - Updated dependencies [
32c3c4f
] - Updated dependencies [
533d6d5
]- @graphql-tools/stitch@6.2.4
- @graphql-tools/wrap@6.2.4
- @graphql-tools/import@6.2.4
- @graphql-tools/merge@6.2.4
- @graphql-tools/utils@6.2.4
- @graphql-tools/delegate@6.2.4
- @graphql-tools/batch-delegate@6.2.4
- @graphql-tools/graphql-tag-pluck@6.2.4
- @graphql-tools/links@6.2.4
- @graphql-tools/load@6.2.4
- @graphql-tools/code-file-loader@6.2.4
- @graphql-tools/git-loader@6.2.4
- @graphql-tools/github-loader@6.2.4
- @graphql-tools/graphql-file-loader@6.2.4
- @graphql-tools/json-file-loader@6.2.4
- @graphql-tools/module-loader@6.2.4
- @graphql-tools/url-loader@6.2.4
- @graphql-tools/mock@6.2.4
- @graphql-tools/relay-operation-optimizer@6.2.4
- @graphql-tools/resolvers-composition@6.2.4
- @graphql-tools/schema@6.2.4
- @graphql-tools/load-files@6.2.4
v6.2.3
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
- Update dependencies
🚀 Features
v6.2.2
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🧰 Enhancements
🐛 Bug Fixes
- Handle recursive input types when pruning schemas @mdlavin (#2023)
- Increase maxBuffer to 1MB @standy (#2018)
v6.2.1
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🧰 Enhancements
- enhance(stitch): simplify subschema sets @yaacovCR (#2001)
- enhance(stitch): introduce SubschemaSetConfig @yaacovCR (#1994)
- enhance(stitching): improve query batching @yaacovCR (#1987)
- enhance(typeMerging): add options @yaacovCR (#1982)
🐛 Bug Fixes
- fix(url-loader): should preserve ws and http in the middle of a pointer @kamilkisiela (#1991)
- fix(stitch) fix abstract type merge failure @gmac (#1981)
- fix(typeMerging): fix scalar type merging @yaacovCR (#1980)
v6.2.0
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
- enable batch execution @yaacovCR (#1971)
🐛 Bug Fixes
- Support InputObjectTypeDefinition & InputObjectTypeExtension for getFieldsWithDirectives @danstarns (#1934)
- fix(mocking): support subscriptions @ardatan (#1952)
- fix(typeMerging): field selection sets @yaacovCR (#1958)
v6.1.0
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🧰 Enhancements
- Expand extended interface selections for subservice compatibility @gmac (#1912)
- streamline imports @yaacovCR (#1940)
- Transforms for normalizing stitched subschema deprecations @gmac (#1925)
- refactor(typesContainSelectionSet): memoize @yaacovCR (#1921)
🐛 Bug Fixes
- fix(build-operation-for-field): respect field depth @ardatan (#1953)
- fix(typeMerging): fix interface merging @yaacovCR (#1917)
v6.0.18
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
✏️ Docs
- Fix build:api-docs @danielrearden (#1899)
🧰 Enhancements
- enhance(load/utils): Improved
parse
to support converting comments into descriptions @dotansimha (#1900) - enhance(stitching): increase key flexibility when type merging @yaacovCR (#1888)
v6.0.17
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
🐛 Bug Fixes
- fix(url-loader): pass variables correctly on HTTP GET @ardatan (#1898)
- fix: change use of
instanceof Promise
to useis-promise
library @cajames (#1837)
v6.0.16
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
- fix(webpack-loader): use javascript compatible with IE @kamilkisiela (#1886)
🧰 Enhancements
- chore(batchDelegate): fix property names @yaacovCR (#1868)
- Make batch delegate send key arrays to loadMany @gmac (#1865)
- chore(batchDelegate): add tests, docs @yaacovCR (#1856)
- refactor(batchDelegate): simplify batch delegation @yaacovCR (#1855)
- Ensure UrlLoader uses introspection options @danielrearden (#1854)
- feat(batch-delegate): added mapping function to createBatchDelegateFn @jakeblaxon (#1825)
- Pull code from unmaintained prisma-yml package into prisma-loader package. @andrewmcgivery (#1841)
- feat(stitch): allow subschemas to not provide queries for merging @yaacovCR (#1842)
- Pluck from @apollo/client/core and apollo-angular @kamilkisiela (#1831)
🐛 Bug Fixes
- fix(mapSchema): mapping fields to new types @yaacovCR (#1877)
- fix(createRequest): selectionSet overrides fieldNodes @yaacovCR (#1820)
- Fix issue with graphql-upload-client @danielrearden (#1838)
v6.0.15
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
- Use improved fork of
graphql-tag/loader
(more customizable, much smaller output, bundle size improvements) @kamilkisiela (#1815) - Helper + docs for selectionSet arguments @gmac (#1802)
🧰 Enhancements
- Refactor GitLoader @danielrearden (#1796)
🐛 Bug Fixes
- Fix GraphQLFileLoader #import syntax handling @danielrearden (#1808)
- fix(transforms): preserve aliases @yaacovCR (#1799)
- fix and actually introduce dynamic selection sets @yaacovCR (#1798)
v6.0.14
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
- introduce TransformEnumValues @yaacovCR (#1769)
🧰 Enhancements
- feat(merge): support multidimensional arrays for mergeTypeDefs and mergeResolvers @ardatan (#1789)
🐛 Bug Fixes
- fix(utils): avoid global variable @ardatan (#1791)
- fix public signatures for strict option @yaacovCR (#1783)
v6.0.13
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
- allow selectionSet hints for stitching to be functions @yaacovCR (#1766)
- Introduce batch delegation @yaacovCR (#1735)
- allow merging scalars @yaacovCR (#1746)
- use memoization when type merging with lists @yaacovCR (#1728)
- Introduce result visiting @yaacovCR (#1718)
- standardize ExecutionResult @yaacovCR (#1727)
- allow mutation type wrapping @yaacovCR (#1723)
🧰 Enhancements
- refactor out renameTypes function @yaacovCR (#1768)
- refactor to rely on mapSchema @yaacovCR (#1767)
- fix express-graphql usage @yaacovCR (#1736)
🐛 Bug Fixes
- fix(url-loader): send correct data if useGETForQueries is true @ardatan (#1778)
- Modify ast nodes when transforming schemas @yaacovCR (#1762)
- fixes selectionSet hints with WrapFields transform @yaacovCR (#1757)
v6.0.12
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🐛 Bug Fixes
- fix(loadSchema): add optional chaining @jameslahm (#1696)
- Use DocumentNode instead of GraphQLResolveInfo to decide the HTTP method for useGETForQueries @ardatan (#1716)
- Name operations @yaacovCR (#1700)
- Fixes for complex type merging @yaacovCR (#1699)
v6.0.11
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
🐛 Bug Fixes
- Use non-node friendly aggregate error @ardatan (#1683)
- fix(merge): add default value for
mergeDirectives
@rufman (#1671) - fix for missing enum in build operation node for field method @brense (#1681)
- fix(proxiedResults): handle top level errors when using type merging @nicolas-cherel (#1648)
- fix(stitching): avoid duplicate directives @yaacovCR (#1665)
- fix combination of type merging and gateway type extensions @yaacovCR (#1664)
v6.0.10
Come talk to us directly on our Discord channel Contact us here: the-guild.dev
What’s Changed
🚀 Features
- improve type merging @yaacovCR (#1636)
- introduce pruneSchema function, PruneSchema transform, and pruneSchema options for makeExecutableSchema and stitchSchemas @yaacovCR (#1632)
🐛 Bug Fixes
- Use aggregate-error instead of CombinedError implementation to keep the content of errors @ardatan (#1646)
- fix by getting underlying type prior to delegation @yaacovCR (#1639)
- fix(typeMerging): can't return a list of merged types @nicolas-cherel (#1635)
- Fix pruning types x2 @yaacovCR (#1638)
- fix(pruningOptions): options are optional @yaacovCR (#1637)
- fix(stitchSchemas): subschemas with object inputs and mergeTypes as true causes crash @nicolas-cherel (#1631)
- transforms should always pass along unmodified parts of originalRequest @yaacovCR ([#1633](https://togithub.com/ardatan/gra
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.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.