@graphql-codegen/visitor-plugin-common

Patch Changes

• 0b090e31a: Apply proper indentation to DirectiveArgs types

Minor Changes

• d84afec09: Support TypeScript ESM modules ("module": "node16" and "moduleResolution": "node16").

  More information on the TypeScript Release Notes.

Patch Changes

• Updated dependencies [68bb30e19]
• Updated dependencies [d84afec09]
• Updated dependencies [a4fe5006b]
• Updated dependencies [8e44df58b]
  • @graphql-codegen/visitor-plugin-common@2.11.0
  • @graphql-codegen/plugin-helpers@2.5.0

Minor Changes

• d6c2d4c09: Allow declaring Argument and InputType field mappings based on directive annotations.

  WARNING: Using this option does only change the type definitions.

  For actually ensuring that a type is correct at runtime you will have to use schema transforms (e.g. with @graphql-tools/utils mapSchema) that apply those rules! Otherwise, you might end up with a runtime type mismatch which could cause unnoticed bugs or runtime errors.

  Please use this configuration option with care!

  plugins:
    config:
      directiveArgumentAndInputFieldMappings:
        asNumber: number
  

  directive @asNumber on ARGUMENT_DEFINITION | INPUT_FIELD_DEFINITION
  
  input MyInput {
    id: ID! @asNumber
  }
  
  type User {
    id: ID!
  }
  
  type Query {
    user(id: ID! @asNumber): User
  }
  

  Usage e.g. with typescript-resolvers

  const Query: QueryResolvers = {
    user(_, args) {
      // args.id is of type 'number'
    }
  }
  

• 5086791ac: Allow overwriting the resolver type signature based on directive usages.

  WARNING: Using this option does only change the generated type definitions.

  For actually ensuring that a type is correct at runtime you will have to use schema transforms (e.g. with @graphql-tools/utils mapSchema) that apply those rules! Otherwise, you might end up with a runtime type mismatch which could cause unnoticed bugs or runtime errors.

  Example configuration:

  config:
    # This was possible before
    customResolverFn: ../resolver-types.ts#UnauthenticatedResolver
    # This is new
    directiveResolverMappings:
      authenticated: ../resolvers-types.ts#AuthenticatedResolver
  

  Example mapping file (resolver-types.ts):

  export type UnauthenticatedContext = {
    user: null
  }
  
  export type AuthenticatedContext = {
    user: { id: string }
  }
  
  export type UnauthenticatedResolver<TResult, TParent, _TContext, TArgs> = (
    parent: TParent,
    args: TArgs,
    context: UnauthenticatedContext,
    info: GraphQLResolveInfo
  ) => Promise<TResult> | TResult
  
  export type AuthenticatedResolver<TResult, TParent, _TContext, TArgs> = (
    parent: TParent,
    args: TArgs,
    context: AuthenticatedContext,
    info: GraphQLResolveInfo
  ) => Promise<TResult> | TResult
  

  Example Schema:

  directive @authenticated on FIELD_DEFINITION
  
  type Query {
    yee: String
    foo: String @authenticated
  }
  

Patch Changes

• feeae1c66: Do not throw an error when trying to merge inline fragment usages.

Patch Changes

• 6470e6cc9: fix(plugin-helpers): remove unnecessary import
• 263570e50: Don't generate duplicate imports for the same identifier
• Updated dependencies [6470e6cc9]
• Updated dependencies [35199dedf]
  • @graphql-codegen/plugin-helpers@2.1.1

Patch Changes

• aabeff181: Don't generate import statements for fragments declared in the file we're outputting to

Minor Changes

• 290170262: add getOperationVariableName function to ClientSideBasePluginConfig class
• 440172cfe: support ESM

Patch Changes

• 24185985a: bump graphql-tools package versions
• Updated dependencies [24185985a]
• Updated dependencies [39773f59b]
• Updated dependencies [440172cfe]
  • @graphql-codegen/plugin-helpers@2.1.0