swagger-typescript-api 13.7.0

v13.7.0

on Node.js NPM

Minor Changes

• beccbaa Thanks @js2me! - Add typeNameSeparator config option for joining typePrefix, type name,
  and typeSuffix in TypeNameFormatter.

  This separator is primarily effective with disableFormatTypeNames: true,
  or when custom hooks.onFormatTypeName preserves separators without
  normalization.

• 162739a Thanks @js2me! - Add disableFormatTypeNames option to disable type name formatting
  and normalization in the generator.

  When enabled, generated names keep raw separators (for example,
  Foo_Bar stays Foo_Bar), which prevents collisions caused by
  startCase-based normalization (such as Foo_Bar and FooBar
  both becoming FooBar).

  The option is available in config and via CLI as
  --disable-format-type-names, and is covered by a dedicated
  spec test in tests/spec/disableFormatTypeNames.

Patch Changes

• #1726 1b60264 Thanks @mlewando-cp! - Dedupe colliding TypeScript identifiers produced by the TypeNameFormatter.

  Two OpenAPI schema keys that differ only in separator placement — e.g.
  Foo_Bar and FooBar — used to collapse to the same identifier via
  startCase + whitespace-strip and emit two export interface FooBar
  declarations (TS2717 whenever the shapes differed).

  TypeNameFormatter now exposes a precommit(rawNames) method the generator
  calls once after loading schema components and before schema parsing. It
  resolves every raw name in two passes — canonical names (raw === formatted
  output) claim their slot first, then non-canonical names suffix-until-free —
  so user-declared identifiers like FooBar1 are preserved regardless of
  source order, and collisions deterministically produce FooBar, FooBar1,
  FooBar2, … References to each schema (including inline generics in route
  handlers) stay consistent with the emitted export interface declarations.

  format() is now a pure cache lookup with a fallback for names discovered
  after precommit (enum keys, extractEnums/extractResponses results). All
  formatting logic is concentrated in a single private computeFormattedName
  helper, so the new behavior composes cleanly with disableFormatTypeNames
  and typeNameSeparator.

  Fixes #1724.