Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency @graphql-tools/schema to v10 #20

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update dependency @graphql-tools/schema to v10 #20

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 23, 2020 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-tools/schema (source) 6.2.4 -> 10.0.6 age adoption passing confidence

Release Notes

ardatan/graphql-tools (@​graphql-tools/schema)

v10.0.6

Compare Source

Patch Changes

v10.0.5

Compare Source

Patch Changes

v10.0.4

Compare Source

Patch Changes

v10.0.3

Compare Source

Patch Changes

v10.0.2

Compare Source

Patch Changes

v10.0.1

Compare Source

Patch Changes

v10.0.0

Compare Source

Major Changes
Patch Changes

v9.0.19

Compare Source

Patch Changes

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

v8.5.1

Compare Source

Patch Changes

v8.5.0

Compare Source

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

v8.4.0

Compare Source

Minor Changes

  • 4914970: mergeSchemas was skipping defaultFieldResolver and defaultMergedResolver by default while extracting resolvers for each given schema to reduce the overhead. But this doesn't work properly if you mix wrapped schemas and local schemas. So new includeDefaultMergedResolver flag is introduced in getResolversFromSchema to put default "proxy" resolvers in the extracted resolver map for mergeSchemas.

    This fixes an issue with alias issue, so nested aliased fields weren't resolved properly because of the missing defaultMergedResolver in the final merged schema which should come from the wrapped schema.

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

  • 722abad: Fix addResolversToSchema bug where type or field processing would be aborted
    prematurely.

    In previous versions, if requireResolversToMatchSchema was set to ignore, although no error
    would be thrown for an unexpected resolver type, type processing would still be aborted early.
    This fix changes the behavior to correctly continue resolver type processing with the next
    provided type.

    In previous versions, if a resolver field began with double underscores, it would correctly be
    used for legacy behavior to directly set a type property, but field processing would be aborted
    early. This fix changes the behavior to correctly continue type processing with the next field.

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
  • 149afdd: fix: getting ready for GraphQL v16
Patch Changes

v8.2.0

Compare Source

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

v8.1.2

Compare Source

Patch Changes

v8.1.1

Compare Source

Patch Changes

v8.1.0

Compare Source

Minor Changes

  • 67691b7: - schemaExtensions option has been added to mergeSchemas, makeExecutableSchema and
    stitchSchemas configurations

    Breaking Changes;

    • Move mergeSchemas and MergeSchemasConfig from @graphql-tools/merge to
      @graphql-tools/schema package to prevent circular dependency between them.
    • mergeSchemasAsync has been removed.
    • Move NamedDefinitionNode, resetComments, collectComment, pushComment and printComment
      from @graphql-tools/merge to @graphql-tools/utils.
Patch Changes

v8.0.3

Compare Source

Patch Changes

v8.0.2

Compare Source

Patch Changes

v8.0.1

Compare Source

Patch Changes

v8.0.0

Compare Source

Major Changes
  • 7d3e300: BREAKING CHANGE
  • 7d3e300: BREAKING CHANGE
    • Remove logger and addErrorLoggingToSchema
      • You can implement logging and debugging mechanism outside the resolvers using some kind of
        plugin system based library like Envelop
  • 7d3e300: BREAKING CHANGE
    • Remove schema level resolvers feature and addSchemaLevelResolver
  • 7d3e300: BREAKING CHANGE
    • No longer exports buildSchemaFromTypeDefinitions, use buildSchema from graphql-js instead
    • Remove allowUndefinedResolve option in makeExecutableSchema because GraphQL Schema itself
      does this checking
Patch Changes

v7.1.5

Compare Source

Patch Changes
  • 22a9f3d: fix(deps): follow package conventions on when to pin

v7.1.4

Compare Source

Patch Changes
  • 61da3e8: use value-or-promise to streamline working with sync values or async promises

v7.1.3

Compare Source

Patch Changes
  • c8e26b8: fix(schema): ignore resolvers if they are not in schema

v7.1.2

Compare Source

Patch Changes

v7.1.0

Compare Source

Minor Changes
  • 4f5a4ef: enhance(schema): add some options to improve schema creation performance
Patch Changes

v7.0.0

Compare Source

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

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)

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

Mocking (addMocksToSchema and @graphql-tools/mock)
  • 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.
Other Utilities (@graphql-tools/utils)
  • 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.

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

@codecov
Copy link

codecov bot commented Oct 23, 2020 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (e4f67a9) to head (e5f5469).

❗ Current head e5f5469 differs from pull request most recent head da2c133

Please upload reports for the commit da2c133 to get more accurate results.

Additional details and impacted files 
@@            Coverage Diff            @@
##            master       #20   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           25        25           
  Branches         7         7           
=========================================
  Hits            25        25

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 8d87d80 to f0689f4 Compare December 9, 2020 08:59
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from f0689f4 to 1fd1e48 Compare February 9, 2021 10:51
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 1fd1e48 to d14f0b9 Compare May 9, 2021 21:33
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from d14f0b9 to c8afb69 Compare October 18, 2021 18:35
@renovate renovate bot changed the title chore(deps): update dependency @graphql-tools/schema to v7 chore(deps): update dependency @graphql-tools/schema to v8 Oct 18, 2021
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from c8afb69 to 546ee57 Compare March 7, 2022 11:02
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 546ee57 to 3393cdb Compare March 26, 2022 14:14
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 3393cdb to 2c2b03b Compare April 24, 2022 20:15
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 2c2b03b to d784f55 Compare May 16, 2022 02:52
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from 9e96353 to b48e0d6 Compare June 23, 2022 18:41
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from b48e0d6 to be6102b Compare September 25, 2022 17:46
@renovate renovate bot changed the title chore(deps): update dependency @graphql-tools/schema to v8 chore(deps): update dependency @graphql-tools/schema to v9 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from be6102b to e5f5469 Compare November 20, 2022 08:06
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from e5f5469 to d6e6ba0 Compare March 18, 2023 18:10
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from d6e6ba0 to 860c7aa Compare April 17, 2023 10:02
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 860c7aa to cca5fe6 Compare May 28, 2023 12:17
@renovate renovate bot changed the title chore(deps): update dependency @graphql-tools/schema to v9 chore(deps): update dependency @graphql-tools/schema to v10 May 28, 2023
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from b07a67d to 4b4b5d3 Compare November 22, 2023 16:05
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 4b4b5d3 to fd2b64d Compare February 23, 2024 15:25
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from fd2b64d to da2c133 Compare May 27, 2024 13:39
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from da2c133 to c22c384 Compare August 12, 2024 00:38
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from c22c384 to 1e75f67 Compare August 16, 2024 03:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants