fix: Update dependency graphql-tools to v9 by renovate[bot] · Pull Request #366 · DanielMSchmidt/apollo-opentracing

b39588c: Deprecate graphql-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 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

Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
Updated dependencies [7d3e300]
- @graphql-tools/schema@8.0.0

`v7.0.5`

Compare Source

Patch Changes

52971f4: fix(graphql-tools): provide @apollo/client as an optional package
Updated dependencies [eae2879]
- @graphql-tools/merge@6.2.14

`v7.0.4`

Compare Source

Patch Changes

Revert mock package to v7 to avoid breaking changes

`v7.0.3`

Compare Source

Patch Changes

Updated dependencies [2492665]
Updated dependencies [2492665]
Updated dependencies [2492665]
- @graphql-tools/delegate@7.0.10
- @graphql-tools/stitch@7.3.0
- @graphql-tools/links@7.0.4
- @graphql-tools/mock@8.0.0

`v7.0.2`

Compare Source

Patch Changes

fb14cd2: Added export from new optimize package
Updated dependencies [fb14cd2]
- @graphql-tools/optimize@1.0.1

`v7.0.1`

Compare Source

Patch Changes

Updated dependencies [294dedd]
Updated dependencies [294dedd]
Updated dependencies [2b6c813]
Updated dependencies [8133a90]
Updated dependencies [2b6c813]
- @graphql-tools/delegate@7.0.1
- @graphql-tools/url-loader@6.3.2
- @graphql-tools/links@7.0.0
- @graphql-tools/utils@7.0.1

`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

Updated dependencies [a925449]
- @graphql-tools/batch-delegate@7.0.0
- @graphql-tools/stitch@7.0.1

Configuration

📅 Schedule: (UTC)

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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

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

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 9 times, most recently from 6a4b05d to 9bec9da Compare October 30, 2020 22:51

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 4 times, most recently from 58398da to f394fef Compare November 8, 2020 16:01

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch from f394fef to 782c720 Compare November 9, 2020 22:11

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 6 times, most recently from 0915509 to 3e0e01a Compare November 22, 2020 20:51

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 3 times, most recently from e46ff72 to aadde31 Compare December 1, 2020 20:18

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 5 times, most recently from ac1a9cf to 0cd9296 Compare December 10, 2020 23:55

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from a4b4dd2 to 9b93ce0 Compare December 15, 2020 23:32

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 5 times, most recently from d625095 to 66038c5 Compare January 26, 2021 09:46

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 3 times, most recently from 88a944e to e267812 Compare January 28, 2021 19:52

renovate Bot changed the title ~~chore(deps): update dependency graphql-tools to v7~~ fix: Update dependency graphql-tools to v7 Jan 28, 2021

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from a03fe27 to 034fbd1 Compare February 17, 2021 14:08

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch from 034fbd1 to dbbddfc Compare May 15, 2021 20:25

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 15fce4b to 7605b73 Compare July 14, 2021 08:08

renovate Bot changed the title ~~fix: Update dependency graphql-tools to v7~~ fix: Update dependency graphql-tools to v8 Jul 28, 2021

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch from 7605b73 to 1244886 Compare July 28, 2021 10:26

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch from 1244886 to 160b245 Compare August 4, 2021 14:46

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 3 times, most recently from cf7e18d to 613be58 Compare August 31, 2021 14:44

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 7c4f53a to 54a75b3 Compare September 8, 2021 13:12

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch from 54a75b3 to 66edb41 Compare September 13, 2021 11:26

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 3 times, most recently from 4e3288f to 727b786 Compare September 25, 2021 16:47

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 9497a0a to 412e792 Compare September 29, 2021 16:19

renovate Bot force-pushed the renovate/major-graphql-tools-monorepo branch from 412e792 to 88e5fe1 Compare October 5, 2021 15:47

fix: Update dependency graphql-tools to v9

01748ff

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: Update dependency graphql-tools to v9#366

fix: Update dependency graphql-tools to v9#366
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/major-graphql-tools-monorepo

renovate Bot commented Oct 24, 2020 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented Oct 24, 2020 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Major Changes

Patch Changes

Patch Changes

renovate Bot commented Oct 24, 2020 •

edited

Loading