Skip to content

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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 1, 2020

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-tools (source) 5.0.0 -> 9.0.18 age adoption passing confidence

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

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

v9.0.6

Compare Source

Patch Changes

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

v8.3.20

Compare Source

Patch Changes

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

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

v8.3.2

Compare Source

Patch Changes

v8.3.1

Compare Source

Patch Changes

v8.3.0

Compare Source

Minor Changes
  • d76a299: Support TypeScript module resolution.
Patch Changes

v8.2.13

Compare Source

Patch Changes

v8.2.12

Compare Source

Patch Changes

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

v8.2.3

Compare Source

Patch Changes

v8.2.2

Compare Source

Patch Changes

v8.2.1

Compare Source

Patch Changes

v8.2.0

Compare Source

Minor Changes
  • c5b0719: feat: GraphQL v16 support
Patch Changes

v8.1.0

Compare Source

Minor Changes

v8.0.0

Compare Source

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

v7.0.5

Compare Source

Patch Changes

v7.0.4

Compare Source

Patch Changes
  • Revert mock package to v7 to avoid breaking changes

v7.0.3

Compare Source

Patch Changes

v7.0.2

Compare Source

Patch Changes

v7.0.1

Compare Source

Patch Changes

v7.0.0

Compare Source

Major Changes
  • a925449: - 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.
    • 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-executable) 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.

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

    • stitchSchemas's mergeTypes option is now true by default! This causes the onTypeConflict
      option to be ignored by default. To use onTypeConflict to select a specific type instead of
      simply merging, simply set mergeTypes to false.

    • schemas argument has been deprecated, use subschemas, typeDefs, or types, depending on
      what you are stitching.

    • When using batch delegation in type merging, the argsFromKeys function is now set only via the
      argsFromKeys property. Previously, if argsFromKeys was absent, it could be read from args.

    • Support for fragment hints has been removed in favor of selection set hints.

    • stitchSchemas now processes all GraphQLSchema and SubschemaConfig subschema input into new
      Subschema objects, handling schema config directives such aso@computed as well as generating
      the final transformed schema, stored as the transformedSchema property, if transforms are
      used. Signatures of the onTypeConflict, fieldConfigMerger, and inputFieldConfigMerger have
      been updated to include metadata related to the original and transformed subschemas. Note the
      property name change for onTypeConflict from schema to subschema.

    • 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, and info
      with parent available as this rather than as the first argument.
    • filterSchema's fieldFilter will now filter all fields across Object, Interface, and Input
      types. For the previous Object-only behavior, switch to the objectFieldFilter option.
    • Unused fieldNodes utility functions have been removed.
    • Unused typeContainsSelectionSet function has been removed, and typesContainSelectionSet has
      been moved to the stitch package.
    • Unnecessary Operation type has been removed in favor of OperationTypeNode from upstream
      graphql-js.
    • As above, applySchemaTransforms/applyRequestTransforms/applyResultTransforms have been
      removed from the utils package, as they are implemented elsewhere or no longer necessary.
Patch Changes

v6.2.6

Compare Source

Patch Changes

v6.2.5

Compare Source

Patch Changes

v6.2.4

Compare Source

Patch Changes

v6.2.3

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

  • Update dependencies

🚀 Features

v6.2.2

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.2.1

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.2.0

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🐛 Bug Fixes

v6.1.0

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🧰 Enhancements

🐛 Bug Fixes

v6.0.18

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

✏️ Docs

🧰 Enhancements

v6.0.17

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

What’s Changed

🚀 Features

🐛 Bug Fixes

v6.0.16

Compare Source

Come talk to us directly on our Discord channel
Contact us here: the-guild.dev

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from d0d0b69 to 473ce63 Compare July 10, 2020 09:57
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 473ce63 to 6a905a9 Compare August 21, 2020 12:00
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 6a905a9 to 73a6691 Compare October 28, 2020 23:00
@renovate renovate bot changed the title Update dependency graphql-tools to v6 (master) Update dependency graphql-tools to v7 (master) Oct 28, 2020
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 73a6691 to e619399 Compare December 12, 2020 01:02
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from e619399 to 8cb0b91 Compare February 11, 2021 11:22
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 8cb0b91 to 665d62b Compare April 26, 2021 12:52
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 665d62b to 28030b0 Compare May 15, 2021 20:42
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 28030b0 to 9b199ed Compare October 20, 2021 05:37
@renovate renovate bot changed the title Update dependency graphql-tools to v7 (master) Update dependency graphql-tools to v8 (master) Oct 20, 2021
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 9b199ed to 27bccee Compare March 26, 2022 16:00
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 27bccee to 8bb9ef7 Compare April 24, 2022 23:36
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 8bb9ef7 to ba3e26a Compare May 15, 2022 22:08
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch 2 times, most recently from 5697772 to 6721a5d Compare June 23, 2022 23:19
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 6721a5d to 815d4d8 Compare September 25, 2022 14:26
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 815d4d8 to 7cad7e1 Compare November 20, 2022 21:33
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 7cad7e1 to 2c8cf8d Compare March 16, 2023 11:13
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 2c8cf8d to 4259fe8 Compare May 29, 2023 15:56
@renovate renovate bot changed the title Update dependency graphql-tools to v8 (master) Update dependency graphql-tools to v9 (master) May 29, 2023
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 4259fe8 to 6819224 Compare February 24, 2024 11:11
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 6819224 to bbe3ef5 Compare October 18, 2024 02:52
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from bbe3ef5 to 259d6e4 Compare November 14, 2024 02:47
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch 2 times, most recently from c71a015 to cb94806 Compare November 28, 2024 02:45
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from cb94806 to 5309b21 Compare December 6, 2024 23:29
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch 2 times, most recently from a35b22a to ec0aee4 Compare December 15, 2024 02:41
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from ec0aee4 to 4232e0c Compare December 25, 2024 18:00
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 4232e0c to 6d75ec1 Compare January 2, 2025 14:43
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 6d75ec1 to c65b955 Compare January 6, 2025 19:04
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from c65b955 to 1a38b44 Compare February 12, 2025 00:03
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch 2 times, most recently from aba74d1 to 421d273 Compare February 26, 2025 03:49
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 421d273 to 39d8717 Compare March 5, 2025 04:02
@renovate renovate bot force-pushed the renovate/master-major-graphql-tools-monorepo branch from 39d8717 to c0ca11b Compare March 15, 2025 00:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants