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

renovate · 2023-05-24T09:21:55Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-codegen/core (source)	`^3.1.0` -> `^4.0.2`
@graphql-codegen/plugin-helpers (source)	`^4.2.0` -> `^5.1.0`
@graphql-codegen/typed-document-node (source)	`^4.0.1` -> `^5.0.11`
@graphql-codegen/typescript (source)	`^3.0.4` -> `^4.1.1`
@graphql-codegen/typescript-operations (source)	`^3.0.4` -> `^4.3.1`
@graphql-codegen/typescript-resolvers (source)	`^3.2.1` -> `^4.4.0`
@graphql-codegen/visitor-plugin-common (source)	`^3.1.1` -> `^5.5.0`

Release Notes

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

`v4.0.2`

Compare Source

Patch Changes

#9813 4e69568 Thanks @saihaj! - bumping for a release
Updated dependencies [4e69568]:
- @graphql-codegen/plugin-helpers @5.0.3

`v4.0.1`

Compare Source

Patch Changes

#9811 d8364e045 Thanks @saihaj! - dependencies updates:
- Updated dependency tslib@~2.6.0 ↗︎ (from ~2.5.0, in dependencies)
Updated dependencies [d8364e045]:
- @graphql-codegen/plugin-helpers @5.0.2

`v4.0.0`

Compare Source

Major Changes

bb66c2a31 Thanks @n1ru4l! - Require Node.js >= 16. Drop support for Node.js 14

Patch Changes

#9449 4d9ea1a5a Thanks @n1ru4l! - dependencies updates:
- Updated dependency @graphql-tools/schema@^10.0.0 ↗︎ (from ^9.0.0, in dependencies)
- Updated dependency @graphql-tools/utils@^10.0.0 ↗︎ (from ^9.1.1, in dependencies)
Updated dependencies [4d9ea1a5a, f46803a8c, 63827fabe, bb66c2a31]:
- @graphql-codegen/plugin-helpers @5.0.0

dotansimha/graphql-code-generator (@graphql-codegen/plugin-helpers)

`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

#9961 dfc5310 Thanks @eddeee888! - Update plugin output type to allow option meta field

`v5.0.3`

Compare Source

Patch Changes

#9813 4e69568 Thanks @saihaj! - bumping for a release

`v5.0.2`

Compare Source

Patch Changes

#9811 d8364e045 Thanks @saihaj! - dependencies updates:
- Updated dependency tslib@~2.6.0 ↗︎ (from ~2.5.0, in dependencies)

`v5.0.1`

Compare Source

Patch Changes

#9523 bb1e0e96e Thanks @tnyo43! - add noSilentErrors option to the config type

`v5.0.0`

Compare Source

Major Changes

bb66c2a31 Thanks @n1ru4l! - Require Node.js >= 16. Drop support for Node.js 14

Patch Changes

#9449 4d9ea1a5a Thanks @n1ru4l! - dependencies updates:
- Updated dependency @graphql-tools/utils@^10.0.0 ↗︎ (from ^9.0.0, in dependencies)
#9332 f46803a8c Thanks @eddeee888! - Update GitHub loader TypeScript type and usage docs
#9360 63827fabe Thanks @beerose! - Add handleAsSDL property to UrlSchemaOptions type

dotansimha/graphql-code-generator (@graphql-codegen/typed-document-node)

`v5.0.11`

Compare Source

Patch Changes

#10160 c7af639 Thanks @jyasskin! - Allow explicit undefined in additional to optional arguments
Updated dependencies [55a1e9e, a235051]:
- @graphql-codegen/visitor-plugin-common @5.5.0
- @graphql-codegen/plugin-helpers @5.1.0

Major Changes

bb66c2a31 Thanks @n1ru4l! - Require Node.js >= 16. Drop support for Node.js 14

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 @&#8203;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

Updated dependencies [4d9ea1a5a, 4d9ea1a5a, f46803a8c, 3848a2b73, ba84a3a27, 63827fabe, 50471e651, 5aa95aa96, ca02ad172, e1dc75f3c, bb66c2a31, 5950f5a68, 5aa95aa96]:
- @graphql-codegen/plugin-helpers @5.0.0
- @graphql-codegen/visitor-plugin-common @4.0.0

dotansimha/graphql-code-generator (@graphql-codegen/typescript)

`v4.1.1`

Compare Source

Patch Changes

Updated dependencies [55a1e9e, a235051]:
- @graphql-codegen/visitor-plugin-common @5.5.0
- @graphql-codegen/plugin-helpers @5.1.0

`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

Updated dependencies [3f4f546]:
- @graphql-codegen/visitor-plugin-common @5.4.0

`v4.0.9`

Compare Source

Patch Changes

Updated dependencies [79fee3c]:
- @graphql-codegen/visitor-plugin-common @5.3.1

`v4.0.8`

Compare Source

Patch Changes

Updated dependencies [808ada5, 14ce39e]:
- @graphql-codegen/visitor-plugin-common @5.3.0

`v4.0.7`

Compare Source

Patch Changes

Updated dependencies [dfc5310, 156cc2b, dfc5310, b49457b]:
- @graphql-codegen/plugin-helpers @5.0.4
- @graphql-codegen/visitor-plugin-common @5.2.0

`v4.0.6`

Compare Source

Patch Changes

Updated dependencies [920b443, ed9c205]:
- @graphql-codegen/visitor-plugin-common @5.1.0

`v4.0.5`

Compare Source

Patch Changes

Updated dependencies [53f270a]:
- @graphql-codegen/visitor-plugin-common @5.0.0

`v4.0.4`

Compare Source

Patch Changes

#9813 4e69568 Thanks @saihaj! - bumping for a release
Updated dependencies [4e69568]:
- @graphql-codegen/visitor-plugin-common @4.1.2
- @graphql-codegen/schema-ast @4.0.2
- @graphql-codegen/plugin-helpers @5.0.3

`v4.0.3`

Compare Source

Patch Changes

Updated dependencies [7718a8113]:
- @graphql-codegen/visitor-plugin-common @4.1.1

`v4.0.2`

Compare Source

Patch Changes

#9811 d8364e045 Thanks @saihaj! - dependencies updates:
- Updated dependency tslib@~2.6.0 ↗︎ (from ~2.5.0, in dependencies)
Updated dependencies [d8364e045, d8364e045, d8364e045, d8364e045, d8364e045]:
- @graphql-codegen/plugin-helpers @5.0.2
- @graphql-codegen/schema-ast @4.0.1
- @graphql-codegen/visitor-plugin-common @4.1.0

`v4.0.1`

Compare Source

Patch Changes

#9497 2276708d0 Thanks @eddeee888! - Revert default ID scalar input type to string

We changed the ID Scalar input type from string to string | number in the latest major version of typescript plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends on typescript plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.
Updated dependencies [2276708d0]:
- @graphql-codegen/visitor-plugin-common @4.0.1

`v4.0.0`

Compare Source

Major Changes

#9375 ba84a3a27 Thanks @eddeee888! - Implement Scalars with input/output types

In GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:

A client may send string or number in the input
A client receives string in its selection set (i.e output)
A server receives string in the resolver (GraphQL parses string or number received from the client to string)
A server may return string or number (GraphQL serializes the value to string before sending it to the client )

Currently, we represent every Scalar with only one type. This is what codegen generates as base type:

export type Scalars = {
  ID: string;
};

Then, this is used in both input and output type e.g.

export type Book = {
  __typename?: 'Book';
  id: Scalars['ID']; // Output's ID can be `string` 👍
};

export type QueryBookArgs = {
  id: Scalars['ID']; // Input's ID can be `string` or `number`. However, the type is only `string` here 👎
};

This PR extends each Scalar to have input and output:

export type Scalars = {
  ID: {
    input: string | number;
    output: string;
  };
};

Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:

export type Book = {
  __typename?: 'Book';
  id: Scalars['ID']['output']; // Output's ID can be `string` 👍
};

export type QueryBookArgs = {
  id: Scalars['ID']['input']; // Input's ID can be `string` or `number` 👍
};

Note that for typescript-resolvers, the type of ID needs to be inverted. However, the referenced types in GraphQL input/output types should still work correctly:

export type Scalars = {
  ID: {
    input: string;
    output: string | number;
  }
}

export type Book = {
  __typename?: "Book";
  id: Scalars["ID"]['output']; // Resolvers can return `string` or `number` in ID fields 👍
};

export type QueryBookArgs = {
  id: Scalars["ID"]['input']; // Resolvers receive `string` in ID fields 👍
};

export type ResolversTypes = {
  ID: ID: ResolverTypeWrapper<Scalars['ID']['output']>; // Resolvers can return `string` or `number` in ID fields 👍
}

export type ResolversParentTypes = {
  ID: Scalars['ID']['output']; // Resolvers receive `string` or `number` from parents 👍
};

Config changes:

Scalars option can now take input/output types:

config: {
  scalars: {
    ID: {
      input: 'string',
      output: 'string | number'
    }
  }
}

If a string is given (instead of an object with input/output fields), it will be used as both input and output types:

config: {
  scalars: {
    ID: 'string'; // This means `string` will be used for both ID's input and output types
  }
}

BREAKING CHANGE: External module Scalar types need to be an object with input/output fields

config: {
  scalars: {
    ID: './path/to/scalar-module';
  }
}

If correctly, wired up, the following will be generated:

// Previously, imported `ID` type can be a primitive type, now it must be an object with input/output fields
import { ID } from './path/to/scalar-module';

export type Scalars = {
  ID: { input: ID['input']; output: ID['output'] };
};

BREAKING CHANGE: This changes Scalar types which could be referenced in other plugins. If you are a plugin maintainer and reference Scalar, please update your plugin to use the correct input/output types.

bb66c2a31 Thanks @n1ru4l! - Require Node.js >= 16. Drop support for Node.js 14

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 @&#8203;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;

#9304 e1dc75f3c Thanks @esfomeado! - Added support for disabling suffixes on Enums.

Patch Changes

Updated dependencies [4d9ea1a5a, 4d9ea1a5a, 4d9ea1a5a, f46803a8c, 3848a2b73, ba84a3a27, 63827fabe, 50471e651, 5aa95aa96, ca02ad172, e1dc75f3c, bb66c2a31, 5950f5a68, 5aa95aa96]:
- @graphql-codegen/plugin-helpers @5.0.0
- @graphql-codegen/schema-ast @4.0.0
- @graphql-codegen/visitor-plugin-common @4.0.0

dotansimha/graphql-code-generator (@graphql-codegen/typescript-operations)

`v4.3.1`

Compare Source

Patch Changes

Updated dependencies [55a1e9e, a235051]:
- @graphql-codegen/visitor-plugin-common @5.5.0
- @graphql-codegen/plugin-helpers @5.1.0
- @graphql-codegen/typescript @4.1.1

`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

Updated dependencies [3f4f546]:
- @graphql-codegen/visitor-plugin-common @5.4.0
- @graphql-codegen/typescript @4.1.0

`v4.2.3`

Compare Source

Patch Changes

Updated dependencies [79fee3c]:
- @graphql-codegen/visitor-plugin-common @5.3.1
- @graphql-codegen/typescript @4.0.9

`v4.2.2`

Compare Source

Patch Changes

Updated dependencies [808ada5, 14ce39e]:
- @graphql-codegen/visitor-plugin-common @5.3.0
- @graphql-codegen/typescript @4.0.8

`v4.2.1`

Compare Source

Patch Changes

Updated dependencies [dfc5310, 156cc2b, dfc5310, b49457b]:
- @graphql-codegen/plugin-helpers @5.0.4
- @graphql-codegen/visitor-plugin-common @5.2.0
- @graphql-codegen/typescript @4.0.7

`v4.2.0`

Compare Source

Minor

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 bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 6 times, most recently from a783da4 to f435bd4 Compare May 31, 2023 18:57

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 bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 12 times, most recently from f8cb419 to b71c1c2 Compare June 21, 2023 05:20

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 bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 4 times, most recently from e8c43bf to 921b2fd Compare October 9, 2024 01:30

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 6 times, most recently from b23a12d to ddf5fc3 Compare October 19, 2024 06:22

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 9 times, most recently from f4d48ff to 33f130c Compare October 29, 2024 04:49

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 7 times, most recently from 115a95f to 9d0672d Compare November 5, 2024 08:24

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from cc965e7 to d2e2812 Compare November 13, 2024 22:43

fix(deps): update graphqlcodegenerator monorepo

767544f

renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from d2e2812 to 767544f Compare November 14, 2024 21:28

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

renovate bot commented May 24, 2023 •

edited

Loading

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

Are you sure you want to change the base?

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

Conversation

renovate bot commented May 24, 2023 • edited Loading

Release Notes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Minor 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

Major Changes

Minor 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

Major Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor

Configuration

renovate bot commented May 24, 2023 •

edited

Loading