Skip to content

fix(deps): update graphqlcodegenerator monorepo (major) #581

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

fix(deps): update graphqlcodegenerator monorepo (major) #581

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 24, 2023 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@graphql-codegen/core (source) ^3.1.0 -> ^5.0.0 age confidence
@graphql-codegen/plugin-helpers (source) ^4.2.0 -> ^6.0.0 age confidence
@graphql-codegen/typed-document-node (source) ^4.0.1 -> ^6.0.2 age confidence
@graphql-codegen/typescript (source) ^3.0.4 -> ^5.0.2 age confidence
@graphql-codegen/typescript-operations (source) ^3.0.4 -> ^5.0.2 age confidence
@graphql-codegen/typescript-resolvers (source) ^3.2.1 -> ^5.1.0 age confidence
@graphql-codegen/visitor-plugin-common (source) ^3.1.1 -> ^6.1.0 age confidence

Release Notes

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

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes
Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/plugin-helpers)

v6.0.0

Compare Source

Major Changes

  • #​10218 140298a Thanks @​eddeee888! - BREAKING CHANGES: Do not generate __isTypeOf for non-implementing types or non-union members

  • #​10218 140298a Thanks @​eddeee888! - Remove deprecated option watchConfig

  • #​10218 140298a Thanks @​eddeee888! - Ensure Federation Interfaces have __resolveReference if they are resolvable entities

    BREAKING CHANGES: Deprecate onlyResolveTypeForInterfaces because majority of use cases cannot implement resolvers in Interfaces.
    BREAKING CHANGES: Deprecate generateInternalResolversIfNeeded.__resolveReference because types do not have __resolveReference if they are not Federation entities or are not resolvable. Users should not have to manually set this option. This option was put in to wait for this major version.

  • #​10218 140298a Thanks @​eddeee888! - BREAKING CHANGE: Improve Federation Entity's resolvers' parent param type: These types were using reference types inline. This makes it hard to handle mappers. The Parent type now all comes from ParentResolverTypes to make handling mappers and parent types simpler.

  • #​10218 140298a Thanks @​eddeee888! - Fix mappers usage with Federation

    mappers was previously used as __resolveReference's first param (usually called "reference"). However, this is incorrect because reference interface comes directly from @key and @requires directives. This patch fixes the issue by creating a new FederationTypes type and use it as the base for federation entity types when being used to type entity references.

    BREAKING CHANGES: No longer generate UnwrappedObject utility type, as this was used to support the wrong previously generated type.

  • #​10218 140298a Thanks @​eddeee888! - Drop Node 18 support

Minor Changes
Patch Changes

v5.1.1

Compare Source

Patch Changes
  • #​10150 e324382 Thanks @​ArminWiebigke! - Allow functions to be passed as valid values for UrlSchemaOptions.customFetch. This was already possible, but the type definitions did not reflect that correctly.

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

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typed-document-node)

v6.0.2

Compare Source

Patch Changes

v6.0.1

Compare Source

Patch Changes

v6.0.0

Compare Source

Major Changes
Patch Changes

v5.1.2

Compare Source

Patch Changes

v5.1.1

Compare Source

Patch Changes

v5.1.0

Compare Source

Minor Changes

v5.0.15

Compare Source

Patch Changes

v5.0.14

Compare Source

Patch Changes

v5.0.13

Compare Source

Patch Changes

v5.0.12

Compare Source

Patch Changes

v5.0.11

Compare Source

Patch Changes

v5.0.10

Compare Source

Patch Changes

v5.0.9

Compare Source

Patch Changes

v5.0.8

Compare Source

Patch Changes

v5.0.7

Compare Source

Patch Changes

v5.0.6

Compare Source

Patch Changes

v5.0.5

Compare Source

Patch Changes

v5.0.4

Compare Source

Patch Changes

v5.0.3

Compare Source

Patch Changes

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Minor Changes

  • #​9196 3848a2b73 Thanks @​beerose! - Add @defer directive support

    When a query includes a deferred fragment field, the server will return a partial response with the non-deferred fields first, followed by the remaining fields once they have been resolved.

    Once start using the @defer directive in your queries, the generated code will automatically include support for the directive.

    // src/index.tsx
import { graphql } from './gql'
const OrdersFragment = graphql(`
  fragment OrdersFragment on User {
    orders {
      id
      total
    }
  }
`)
const GetUserQuery = graphql(`
  query GetUser($id: ID!) {
    user(id: $id) {
      id
      name
      ...OrdersFragment @​defer
    }
  }
`)

    The generated type for GetUserQuery will have information that the fragment is incremental, meaning it may not be available right away.

    // gql/graphql.ts
export type GetUserQuery = { __typename?: 'Query'; id: string; name: string } & ({
  __typename?: 'Query'
} & {
  ' $fragmentRefs'?: { OrdersFragment: Incremental<OrdersFragment> }
})

    Apart from generating code that includes support for the @defer directive, the Codegen also exports a utility function called isFragmentReady. You can use it to conditionally render components based on whether the data for a deferred
    fragment is available:

    const OrdersList = (props: { data: FragmentType<typeof OrdersFragment> }) => {
  const data = useFragment(OrdersFragment, props.data);
  return (
    // render orders list
  )
};

function App() {
  const { data } = useQuery(GetUserQuery);
  return (
    {data && (
      <>
        {isFragmentReady(GetUserQuery, OrdersFragment, data)
					&& <OrdersList data={data} />}
      </>
    )}
  );
}
export default App;
Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.1.6

Compare Source

Patch Changes

v4.1.5

Compare Source

Patch Changes

v4.1.4

Compare Source

Patch Changes

v4.1.3

Compare Source

Patch Changes

v4.1.2

Compare Source

Patch Changes

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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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/major-graphqlcodegenerator-monorepo branch 6 times, most recently from a783da4 to f435bd4 Compare May 31, 2023 18:57
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 6 times, most recently from 7abc0c3 to 01f9f38 Compare June 9, 2023 14:44
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 12 times, most recently from f8cb419 to b71c1c2 Compare June 21, 2023 05:20
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 6 times, most recently from bc5495a to cd383ca Compare June 26, 2023 09:59
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 7 times, most recently from 36f5d87 to f463383 Compare September 21, 2025 01:39
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 10 times, most recently from 20b1f44 to 391ae46 Compare October 1, 2025 21:52
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 639a20c to 5ac07a5 Compare October 6, 2025 16:28
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 6 times, most recently from 5a0ccf8 to e76bb58 Compare October 15, 2025 10:55
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 0e67696 to 9cca459 Compare October 21, 2025 09:39
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 9cca459 to 53f1d4c Compare October 22, 2025 11:49
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