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.

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

Update graphqlcodegenerator monorepo #15

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-codegen/add (source) 5.0.0 -> 5.0.3 age adoption passing confidence
@graphql-codegen/cli (source) 5.0.0 -> 5.0.3 age adoption passing confidence
@graphql-codegen/typescript (source) 4.0.1 -> 4.1.1 age adoption passing confidence
@graphql-codegen/typescript-resolvers (source) 4.0.1 -> 4.4.0 age adoption passing confidence

Release Notes

dotansimha/graphql-code-generator (@​graphql-codegen/add)

v5.0.3

Compare Source

Patch Changes
  • #​9987 5501c62 Thanks @​taro-28! - Export configuration types (e.g. AddPluginConfig) from the entry point.

    import type { AddPluginConfig } from '@​graphql-codegen/add';

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/cli)

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v4.1.1

Compare Source

Patch Changes

v4.1.0

Compare Source

Minor Changes
  • #​10077 3f4f546 Thanks @​eddeee888! - Extend config.avoidOptions to support query, mutation and subscription

    Previously, config.avoidOptions.resolvers was being used to make query, mutation and subscription fields non-optional.
    Now, config.avoidOptions.query, config.avoidOptions.mutation and config.avoidOptions.subscription can be used to target the respective types.

Patch Changes

v4.0.9

Compare Source

Patch Changes

v4.0.8

Compare Source

Patch Changes

v4.0.7

Compare Source

Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typescript-resolvers)

v4.4.0

Compare Source

Minor Changes
  • #​9989 55a1e9e Thanks @​eddeee888! - Add generateInternalResolversIfNeeded option

    This option can be used to generate more correct types for internal resolvers. For example, only generate __resolveReference if the federation object has a resolvable @key.

    In the future, this option can be extended to support other internal resolvers e.g. __isTypeOf is only generated for implementing types and union members.

  • #​10141 a235051 Thanks @​eddeee888! - Add avoidCheckingAbstractTypesRecursively to avoid checking and generating abstract types recursively

    For users that already sets recursive default mappers e.g. Partial<{T}> or DeepPartial<{T}>, having both options on will cause a nested loop which eventually crashes Codegen. In such case, setting avoidCheckingAbstractTypesRecursively: true allows users to continue to use recursive default mappers as before.

Patch Changes

v4.3.0

Compare Source

Minor Changes
  • #​10077 3f4f546 Thanks @​eddeee888! - Extend config.avoidOptions to support query, mutation and subscription

    Previously, config.avoidOptions.resolvers was being used to make query, mutation and subscription fields non-optional.
    Now, config.avoidOptions.query, config.avoidOptions.mutation and config.avoidOptions.subscription can be used to target the respective types.

Patch Changes

v4.2.1

Compare Source

Patch Changes

v4.2.0

Compare Source

Minor Changes
Patch Changes

v4.1.0

Compare Source

Minor Changes
  • #​9961 dfc5310 Thanks @​eddeee888! - Update typescript-resolvers to report generated resolver types in the run to meta field in the output
Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

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.

👻 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/graphqlcodegenerator-monorepo branch 2 times, most recently from 38c746b to b97e761 Compare February 23, 2024 02:12
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from b97e761 to d4d2728 Compare April 16, 2024 17:53
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from d4d2728 to 6533445 Compare May 23, 2024 02:46
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from 6533445 to 0a991bc Compare June 6, 2024 08:45
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from 0a991bc to 4405cda Compare June 15, 2024 08:20
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch 2 times, most recently from e149918 to a94ff9c Compare July 3, 2024 17:44
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from a94ff9c to 4ec118d Compare August 7, 2024 23:56
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from 4ec118d to cb52259 Compare October 9, 2024 08:59
@renovate renovate bot force-pushed the renovate/graphqlcodegenerator-monorepo branch from cb52259 to fc60666 Compare October 29, 2024 06:00
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