chore(deps): update graphqlcodegenerator monorepo (major) #16

renovate-bot · 2023-09-07T00:23:11Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@graphql-codegen/add	`^3.1.1` -> `^5.0.0`
@graphql-codegen/cli	`^3.3.1` -> `^5.0.0`
@graphql-codegen/introspection	`^3.0.1` -> `^4.0.0`
@graphql-codegen/typescript	`^3.0.4` -> `^4.0.0`
@graphql-codegen/typescript-operations	`^3.0.4` -> `^4.0.0`

Release Notes

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

`v5.0.0`

Compare Source

Major Changes

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

Patch Changes

Updated dependencies [4d9ea1a5a, f46803a8c, 63827fabe, bb66c2a31]:
- @graphql-codegen/plugin-helpers @5.0.0

`v4.0.1`

Compare Source

Patch Changes

#8879 8206b268d Thanks @renovate! - dependencies updates:
- Updated dependency tslib@~2.5.0 ↗︎ (from ~2.4.0, in dependencies)
Updated dependencies [8206b268d, a118c307a, a3309e63e]:
- @graphql-codegen/plugin-helpers @4.1.0

`v4.0.0`

Compare Source

Major Changes

#8885 fd0b0c813 Thanks @n1ru4l! - drop Node.js 12 support

Patch Changes

Updated dependencies [fc79b65d4, fd0b0c813]:
- @graphql-codegen/plugin-helpers @4.0.0

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

`v5.0.0`

Compare Source

Major Changes

#9506 dd9c7e148 Thanks @valkum! - Make @parcel/watcher optional

Patch Changes

#9513 fdd19d24d Thanks @cichelero! - Update yaml dependency to 2.3.1
Updated dependencies [bb1e0e96e]:
- @graphql-codegen/plugin-helpers @5.0.1

`v4.0.1`

Compare Source

Patch Changes

#9479 0aa444b5d Thanks @gilgardosh! - dependencies updates:
- Updated dependency graphql-config@^5.0.2 ↗︎ (from ^5.0.1, in dependencies)
#9479 0aa444b5d Thanks @gilgardosh! - Update graphql-config to v^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-config@^5.0.0 ↗︎ (from ^4.5.0, in dependencies)
#9449 4d9ea1a5a Thanks @n1ru4l! - dependencies updates:
- Updated dependency @graphql-tools/apollo-engine-loader@^8.0.0 ↗︎ (from ^7.3.6, in dependencies)
- Updated dependency @graphql-tools/code-file-loader@^8.0.0 ↗︎ (from ^7.3.17, in dependencies)
- Updated dependency @graphql-tools/git-loader@^8.0.0 ↗︎ (from ^7.2.13, in dependencies)
- Updated dependency @graphql-tools/github-loader@^8.0.0 ↗︎ (from ^7.3.28, in dependencies)
- Updated dependency @graphql-tools/graphql-file-loader@^8.0.0 ↗︎ (from ^7.5.0, in dependencies)
- Updated dependency @graphql-tools/json-file-loader@^8.0.0 ↗︎ (from ^7.4.1, in dependencies)
- Updated dependency @graphql-tools/load@^8.0.0 ↗︎ (from ^7.8.0, in dependencies)
- Updated dependency @graphql-tools/prisma-loader@^8.0.0 ↗︎ (from ^7.2.69, in dependencies)
- Updated dependency @graphql-tools/url-loader@^8.0.0 ↗︎ (from ^7.17.17, in dependencies)
- Updated dependency @graphql-tools/utils@^10.0.0 ↗︎ (from ^9.0.0, in dependencies)
- Updated dependency cosmiconfig@^8.1.3 ↗︎ (from ^7.0.0, in dependencies)
- Updated dependency graphql-config@^5.0.1 ↗︎ (from ^4.5.0, in dependencies)
#9371 d431f426e Thanks @Axxxx0n! - Fixed option ignoreNoDocuments when using graphql configs
#9275 2a5da5894 Thanks @milesrichardson! - Trigger rebuilds in watch mode while respecting rules of precedence and negation, both in terms of global (top-level) config vs. local (per-output target) config, and in terms of watch patterns (higher priority) vs. documents/schemas (lower priority). This fixes an issue with overly-aggressive rebuilds during watch mode.
Updated dependencies [4d9ea1a5a, 4d9ea1a5a, f46803a8c, 63827fabe, bb66c2a31]:
- @graphql-codegen/core @4.0.0
- @graphql-codegen/plugin-helpers @5.0.0

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

`v4.0.0`

Compare Source

Major Changes

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

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.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.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
- @graphql-codegen/typescript @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, 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
- @graphql-codegen/typescript @4.0.0

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 has been generated by Mend Renovate. View repository job log here.

renovate-bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 48a4c8b to 72d6728 Compare September 7, 2023 09:27

chore(deps): update graphqlcodegenerator monorepo

fd71738

renovate-bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 72d6728 to fd71738 Compare September 7, 2023 11:09

naftis merged commit 458d747 into opencrvs:develop Sep 11, 2023
1 check passed

renovate-bot deleted the renovate/major-graphqlcodegenerator-monorepo branch September 11, 2023 07:59

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(deps): update graphqlcodegenerator monorepo (major) #16

chore(deps): update graphqlcodegenerator monorepo (major) #16

renovate-bot commented Sep 7, 2023 •

edited

Loading

chore(deps): update graphqlcodegenerator monorepo (major) #16

chore(deps): update graphqlcodegenerator monorepo (major) #16

Conversation

renovate-bot commented Sep 7, 2023 • edited Loading

Release Notes

Major Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Major Changes

Patch Changes

Major Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Patch Changes

Major Changes

Minor Changes

Patch Changes

Configuration

renovate-bot commented Sep 7, 2023 •

edited

Loading