fix: update auto merge on patch or minor - #189

v13.1.3

Compare Source

Patch Changes

• #​8575 7fbc6e7 Thanks @​ardatan! - mapSchema now remaps directive argument defaults the same way it already remaps field argument defaults.

  Use case: UserRole is remapped to internal ids, and @auth defaults to USER.

  const schema = mapSchema(originalSchema, {
    [MapperKind.ENUM_VALUE]: (valueConfig, typeName, _schema, externalValue) => {
      if (typeName === 'UserRole' && externalValue === 'USER') {
        return { ...valueConfig, value: '3user' };
      }
      return valueConfig;
    },
  });
  
  // directive @auth(role: UserRole = USER)
  schema.getDirective('auth').args.find(arg => arg.name === 'role').defaultValue;
  // before: "USER"
  // after:  "3user"

  mapSchema serializes the stored default with the source type before parsing with the remapped type, so an internal value that matches another enum name (USER -> "ADMIN") stays "ADMIN" instead of being parsed as that name.

  forEachDefaultValue walks directive arguments too, so makeExecutableSchema enum resolvers get the same result.

• #​8574 5ceed9d Thanks @​ardatan! - Published Executor types include /// <reference lib="esnext.disposable" preserve="true" /> so consumers do not need skipLibCheck or a full esnext lib just to import this package.

  Use case: an app with "lib": ["es2022"] or ["es2024"] and skipLibCheck: false that imports @graphql-tools/utils:

  import type { Executor } from '@graphql-tools/utils';
  
  export const executor: Executor = async request => {
    // ...
  };

  Executor can return a Disposable / AsyncIterable result. Those names live in TypeScript's esnext.disposable lib, which is not part of es2022/es2024. Without the preserved reference, tsc reports Cannot find name 'Disposable'. With it, the published .d.ts pulls in that lib for the consumer automatically.

v13.1.2

Compare Source

Patch Changes

• #​8558 501109b Thanks @​ardatan! - printSchemaWithDirectives no longer turns unquoted directive argument literals into strings.

  In GraphQL SDL, an unquoted identifier in value position is an EnumValue AST node. A quoted value is a StringValue. Those are different kinds even when the argument type is a custom scalar rather than an enum type. parseLiteral on that scalar receives the original kind, so a custom scalar can treat argument_value and "argument_value" as different inputs.

  The printer was reconstructing directive arguments from JS values. valueFromASTUntyped maps both kinds to the same string, and astFromValue then emits a StringValue. The printed SDL became @directive(arg: "argument_value") even though the schema AST still had @directive(arg: argument_value).

  That is a round-trip / fidelity bug: loaders, schema diffs, snapshots, and subgraph publishes see different SDL, and a scalar that distinguishes the two kinds changes meaning. Default scalars coerce both to the same JS string, so many runtime paths do not notice.

  When the original AST is still the source of truth, printSchemaWithDirectives now keeps those directive argument nodes, including nested list and input-object values. If directive values are supplied only through extensions (code-first), JS strings are still printed as strings because the original kind is not available.

  Fixes #​8557

v18.0.9

Compare Source

Changed

• Permit DOTENV_PATH being empty string with the CLI (#​1076)