⬆️ Bump graphql-tools from 4.0.8 to 6.2.5

[dependabot-preview]

Bumps graphql-tools from 4.0.8 to 6.2.5.

Release notes

Sourced from graphql-tools's releases.

@graphql-tools/graphql-tag-pluck@6.2.5

Patch Changes

• e9ed9394: Change intenral API to add more details on found locations, and export parseCode for lower-level parsing
• 54b440a9: allow to skip identation while plucking

@graphql-tools/git-loader@6.2.5

Patch Changes

• Updated dependencies [be1a1575]
  • @graphql-tools/utils@7.0.0
  • @graphql-tools/graphql-tag-pluck@6.2.6

@graphql-tools/links@6.2.5

Patch 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.

Commits

• 9468a46 chore(release): update monorepo packages versions (#2129)
• be1a157 v7 (#1935)
• cdfe6be chore(deps-dev): bump graphql-scalars from 1.3.0 to 1.4.1 (#2127)
• 9cc8023 chore(deps): bump react from 16.13.1 to 16.14.0 (#2114)
• 2250e3f chore(deps): bump graphql-request from 3.1.0 to 3.2.0 (#2112)
• fcfcdbe chore(deps-dev): bump @types/lodash from 4.14.161 to 4.14.162 (#2115)
• 624a9b6 [deploy_website] docs(website): add schema-stitching page back
• adf5e23 chore(deps-dev): bump @typescript-eslint/eslint-plugin (#2108)
• db08daa chore(deps-dev): bump @typescript-eslint/parser from 4.3.0 to 4.4.1 (#2106)
• a2d0c9d chore(deps-dev): bump apollo-server-express from 2.18.1 to 2.18.2 (#2096)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by ardatan, a new releaser for graphql-tools since your current version.

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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[coveralls]

Pull Request Test Coverage Report for Build 115

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.75%

---

Totals
Change from base Build 9:	0.0%
Covered Lines:	56
Relevant Lines:	59

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 115

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 93.75%

---

Totals
Change from base Build 9:	0.0%
Covered Lines:	56
Relevant Lines:	59

---

💛 - Coveralls

[dependabot-preview]

Superseded by #54.