build(deps-dev): bump @graphql-codegen/typescript-resolvers from 3.0.0 to 3.2.1

[dependabot]

Bumps @graphql-codegen/typescript-resolvers from 3.0.0 to 3.2.1.

Changelog

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

3.2.1

Patch Changes

• #9231 402cb8ac0 Thanks @​eddeee888! - Implement resolversNonOptionalTypename for mapper cases

• Updated dependencies [386cf9044, 402cb8ac0]:

  • @​graphql-codegen/visitor-plugin-common@​3.1.1
  • @​graphql-codegen/typescript@​3.0.4

3.2.0

Minor Changes

• #9146 9f4d9c5a4 Thanks @​eddeee888! - [typescript-resolvers] Add resolversNonOptionalTypename config option.

  This is extending on ResolversUnionTypes implemented in dotansimha/graphql-code-generator#9069

  resolversNonOptionalTypename adds non-optional __typename to union members of ResolversUnionTypes, without affecting the union members' base intefaces.

  A common use case for non-optional __typename of union members is using it as the common field to work out the final schema type. This makes implementing the union's __resolveType very simple as we can use __typename to decide which union member the resolved object is. Without this, we have to check the existence of field/s on the incoming object which could be verbose.

  For example, consider this schema:

  type Query {
    book(id: ID!): BookPayload!
  }
  type Book {
  id: ID!
  isbn: String!
  }
  type BookResult {
  node: Book
  }
  type PayloadError {
  message: String!
  }
  union BookPayload = BookResult | PayloadError

  With optional __typename: We need to check existence of certain fields to resolve type in the union resolver:

  // Query/book.ts
  export const book = async () => {

... (truncated)

Commits

• 21050ae chore(release): update monorepo packages versions (#9269)
• 402cb8a [typescript-resolvers] Fix resolversNonOptionalTypename for union members in ...
• 6e3fd38 chore(release): update monorepo packages versions (#9132)
• a5ec5af [testing] Add complex Interface test cases for typescript-resolvers (#9228)
• e567901 [typescript-resolvers] Fix resolvers union types used in `ResolversParentType...
• 9f4d9c5 [typescript-resolvers] Add resolversNonOptionalTypename config (#9146)
• 9c4f104 fix: Resolving issue with nesting fields in provides directive being prevente...
• 9a65d17 chore(release): update monorepo packages versions (#9054)
• ba0610b Custom mappers w. placeholder will apply omit (#9110)
• 4b49f6f [typescript-resolvers] Extract union types to ResolversUnionTypes (#9069)
• 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 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)