Bump @graphql-tools/utils from 6.2.3 to 7.0.2 by dependabot[bot] · Pull Request #622 · SimenB/graphql-code-generator

dependabot · 2020-11-02T12:59:39Z

Bumps @graphql-tools/utils from 6.2.3 to 7.0.2.

Release notes

Sourced from @graphql-tools/utils's releases.

@graphql-tools/utils@7.0.2

Patch Changes

e3176633: fix(utils): revert to old observableToAsyncIterable return type

@graphql-tools/utils@7.0.1

Patch Changes

8133a907: fix(utils): Remove \$ from invalidPathRegex

2b6c813e: fix(utils): fix typing mismatch between linkToSubscriber and observableToAsyncIterable

@graphql-tools/utils@7.0.0

Major Changes

be1a1575: ## Breaking Changes:

Schema Generation and Decoration API (@graphql-tools/schema)

Resolver validation options should now be set to error, warn or ignore rather than true or false. 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 to requireResolversToMatchSchema, to harmonize the naming convention of all the validators. The default setting of requireResolversToMatchSchema is error, matching the previous behavior.

Schema Delegation (delegateToSchema & @graphql-tools/delegate)

The delegateToSchema return value has matured and been formalized as an ExternalObject, 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 including slicedError, getErrors, getErrorsByPathSegment functions. Only external errors with missing or invalid paths must still be preserved by annotating the remote object with special properties. The new getUnpathedErrors function is therefore necessary for retrieving only these errors. Note also the new annotateExternalObject and mergeExternalObjects functions, as well as the renaming of handleResult to resolveExternalValue.

Transform types and the applySchemaTransforms are now relocated to the delegate package; applyRequestTransforms/applyResultTransforms functions have been deprecated, however, as this functionality has been replaced since v6 by the Transformer abstraction.

The transformRequest/transformResult methods are now provided additional delegationContext 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 now provided the subschemaConfig and final (non-executable) transformedSchema parameters. As in v6, the transformSchema 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-executabel) initial result. In v7, the individual transformSchema 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 the transformSchema parameters above.

Remote Schemas & Wrapping (wrapSchema, makeRemoteExecutableSchema, and @graphql-tools/wrap)

wrapSchema and generateProxyingResolvers now only take a single options argument with named properties of type SubschemaConfig. The previously possible shorthand version with first argument consisting of a GraphQLSchema and second argument representing the transforms should be reworked as a SubschemaConfig object.

Similarly, the ICreateProxyingResolverOptions interface that provides the options for the createProxyingResolver property of SubschemaConfig options has been adjusted. The schema property previously could be set to a GraphQLSchema or a SubschemaConfig object. This property has been removed in favor of a subschemaConfig property that will always be a SubschemaConfig object. The transforms property has been removed; transforms should be included 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 fields doing the hard work of proxying. Support for custom merged resolvers throught createMergedResolver 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's wrappingResolver 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 as TransformRootFields or TransformObjectFields.

The ExtendSchema transform has been removed, as it is conceptually simpler just to use stitchSchemas with one subschema.

The ReplaceFieldsWithFragment, AddFragmentsByField, AddSelectionSetsByField, and AddMergedTypeSelectionSets transforms has been removed, as they are superseded by the AddSelectionSets and VisitSelectionSets transforms. The AddSelectionSets 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 the parseSelectionSet function from @graphql-tools/utils.

Schema Stitching (stitchSchemas & @graphql-tools/stitch)

... (truncated)

Commits

e223d16 chore(release): update monorepo packages versions (#2176)
a74f885 chore(packaging): allow patches of local packages (#2178)
e317663 fix(utils): observableToAsyncIterable return type (#2177)
856e23f fix(delegate): WrapConcreteTypes regression (#2174)
b25e16c chore(deps-dev): bump @types/jest from 26.0.14 to 26.0.15 (#2169)
c1edabd chore(release): update monorepo packages versions (#2167)
16bb2fd fix(links): refactor and fix types (#2166)
718eda3 fix(stitch): mergeExternalObjects regressions (#2165)
f07c484 chore(deps-dev): bump jest from 26.5.3 to 26.6.1 (#2160)
d6af037 chore(deps): bump @docusaurus/core from 2.0.0-alpha.65 to 2.0.0-alpha.66 (#2164)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@graphql-tools/utils](https://github.com/ardatan/graphql-tools) from 6.2.3 to 7.0.2. - [Release notes](https://github.com/ardatan/graphql-tools/releases) - [Commits](https://github.com/ardatan/graphql-tools/compare/v6.2.3...@graphql-tools/utils@7.0.2) Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2020-11-02T12:59:41Z

The following labels could not be found: automerge.

dependabot · 2020-11-03T16:10:09Z