chore(deps-dev): bump @graphql-codegen/typescript-operations from 3.0.4 to 4.0.0

[dependabot]

Bumps @graphql-codegen/typescript-operations from 3.0.4 to 4.0.0.

Changelog

Sourced from @​graphql-codegen/typescript-operations's changelog.

4.0.0

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';

... (truncated)

Commits

• 5c7b3b3 Upcoming Release Changes (#9355)
• e1dc75f Added support for enumSuffix (#9304)
• ba84a3a Update typescript, typescript-operations and typescript-resolvers plugins Sca...
• 5950f5a fix: Don't generate invalid type names with mergeFragmentTypes (#9369)
• 3848a2b Add @defer directive support (#9196)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #643.