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

[dependabot]

Bumps @graphql-codegen/typescript-operations from 2.2.0 to 4.0.1.

Release notes

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

Release 2022-08-04T13:12:01.667Z

@​graphql-codegen/graphql-modules-preset@​2.5.0

Minor Changes

• #6796 8b6e8e664 Thanks @​kamilkisiela! - Introduce requireRootResolvers flag

Release 2022-08-04T13:05:23.977Z

No release notes provided.

Release 2022-08-04T13:02:57.827Z

No release notes provided.

@​graphql-codegen/typescript-react-query@​4.0.0

Major Changes

• 5c7592b4d: Introduces breaking changes to support react-query@4.0.0:

  • react query package is now @tanstack/react-query -> import changes
  • introduced a legacyMode flag (false by default)

  /!\ If you are using the 'react-query' package or react-query < 4, please set the legacyMode option to true. /!\

@​graphql-codegen/typescript-urql@​3.6.3

Patch Changes

• ab66ba104: Add useQuery argument generic type

@​graphql-codegen/typescript-react-query@​3.6.2

Patch Changes

• Updated dependencies [2cbcbb371]
  • @​graphql-codegen/visitor-plugin-common@​2.12.0
  • @​graphql-codegen/plugin-helpers@​2.6.0

@​graphql-codegen/typescript-urql@​3.6.2

Patch Changes

• Updated dependencies [2cbcbb371]
  • @​graphql-codegen/visitor-plugin-common@​2.12.0
  • @​graphql-codegen/plugin-helpers@​2.6.0

@​graphql-codegen/typescript-vue-apollo@​3.3.2

Patch Changes

• Updated dependencies [2cbcbb371]
  • @​graphql-codegen/visitor-plugin-common@​2.12.0
  • @​graphql-codegen/plugin-helpers@​2.6.0

@​graphql-codegen/visitor-plugin-common@​2.12.0

... (truncated)

Changelog

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

4.0.1

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

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 = {

... (truncated)

Commits

• a509268 Upcoming Release Changes (#9501)
• 2276708 Revert default ID scalar input type to string (#9497)
• 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)
• 21050ae chore(release): update monorepo packages versions (#9269)
• 6e3fd38 chore(release): update monorepo packages versions (#9132)
• d318805 eslint fixes (#9247)
• Additional commits viewable 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)