Skip to content

Update dependency @graphql-tools/mock to v8 #16

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

Update dependency @graphql-tools/mock to v8 #16

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link

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

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-tools/mock 6.1.0 -> 8.6.13 age adoption passing confidence

Release Notes

ardatan/graphql-tools

v8.6.13

Compare Source

Patch Changes

v8.6.12

Compare Source

Patch Changes

v8.6.11

Compare Source

Patch Changes

v8.6.10

Compare Source

Patch Changes

v8.6.9

Compare Source

Patch Changes

v8.6.8

Compare Source

Patch Changes

v8.6.7

Compare Source

Patch Changes

v8.6.6

Compare Source

Patch Changes

v8.6.5

Compare Source

Patch Changes

v8.6.4

Compare Source

Patch Changes

v8.6.3

Compare Source

Patch Changes

v8.6.2

Compare Source

Patch Changes

v8.6.1

Compare Source

Patch Changes

v8.6.0

Compare Source

Minor Changes
  • 7dcf3d9: feat(mock): ability to add typesafety to IMocks with custom resolver signature

v8.5.3

Compare Source

Patch Changes
  • 72e073f: Resolve an issue with addMocksToSchema where the provided store is ignored

v8.5.2

Compare Source

Patch Changes

v8.5.1

Compare Source

Patch Changes

v8.5.0

Compare Source

Minor Changes
  • e6e9f91: Added relayStylePaginationMock helper

v8.4.4

Compare Source

Patch Changes
  • 3eef5e2: Update deep mocking feature with preserveResolvers for more scenarios

v8.4.3

Compare Source

Patch Changes
  • dc7c998: fix(mock): allow mocking of objects nested in arrays

v8.4.2

Compare Source

Patch Changes

v8.4.1

Compare Source

Patch Changes
  • 99319be: fix(mock): MockStore.has should be true if key is present without data

v8.4.0

Compare Source

Minor Changes
  • d7de7fb: feat(mock): add has method to MockStore
Patch Changes

v8.3.1

Compare Source

Patch Changes
  • 491e961: fix(mock): fix handling _id field name

v8.3.0

Compare Source

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

v8.2.2

Compare Source

Patch Changes

v8.2.1

Compare Source

Patch Changes

v8.2.0

Compare Source

Minor Changes
  • 9a44594: feat(mock): add find and filter methods
Patch Changes

v8.1.8

Compare Source

Patch Changes

v8.1.7

Compare Source

Patch Changes

v8.1.6

Compare Source

Patch Changes

v8.1.5

Compare Source

Patch Changes
  • e7b78fd: Removes ts-is-defined dependency

v8.1.4

Compare Source

Patch Changes

v8.1.3

Compare Source

Patch Changes
  • 702f44e: Avoid __typename does not exist error

v8.1.2

Compare Source

Patch Changes
  • 8e64492: fix(mock): handle null values correctly

v8.1.1

Compare Source

Patch Changes
  • cf794a4: fix(mock): fix missing reset method to IMockStore

v8.1.0

Compare Source

Minor Changes
  • a2e7ff7: feat(mock): add reset method to MockStore

v8.0.0

Compare Source

Major Changes

  • 2492665: Reworked to add state-full behavior to the library:

    • Breaking: mock functions does not receive resolver arguments anymore and can't return promise. Use resolvers option instead.
    • Breaking: when preserved, resolvers will not receive plain object returned by mock anymore as source but rather a Ref that can be used to query the store.
    • Deprecated: MockList is deprecated. Use plain arrays instead.

    See migration guide.

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.

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

Configuration

📅 Schedule: Branch creation - "before 3am on Monday" in timezone Asia/Tokyo, 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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the renovate label Oct 25, 2020
@renovate renovate bot changed the title Update dependency @graphql-tools/mock to v7 Update dependency @graphql-tools/mock to v8 Feb 10, 2021
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 086d920 to 1b622d9 Compare February 10, 2021 19:45
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 1b622d9 to 2cb534b Compare April 26, 2021 15:15
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch 2 times, most recently from fe3a96d to d0a9b9c Compare May 15, 2021 19:57
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from d0a9b9c to 066a180 Compare October 18, 2021 16:56
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 066a180 to 8e6a4fa Compare March 7, 2022 14:02
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 8e6a4fa to be1a93c Compare March 26, 2022 13:21
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from be1a93c to 2e05ef5 Compare April 25, 2022 02:48
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 2e05ef5 to 391e7e7 Compare May 15, 2022 21:10
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 391e7e7 to 70ca09a Compare June 18, 2022 13:24
@renovate renovate bot force-pushed the renovate/major-graphql-tools-monorepo branch from 70ca09a to 19c7e03 Compare June 23, 2022 21:51
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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant