v13.7.2

Patch Changes

• 5f6b28a Thanks @js2me! - yet another fix of the issue #1433 (incorrect yaml multiline parsing)

v13.7.1

Patch Changes

• 189ad98 Thanks @js2me! - fixed normalization external refs in swagger schema

v13.7.0

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.

v13.6.11

Patch Changes

• #1722 586d60b Thanks @tenenger7125! - Add: null to allOf intersection types with nullable(true)

v13.6.10

Patch Changes

• 08026ef Thanks @js2me! - add servers field to route info raw

v13.6.9

Patch Changes

• 756f5aa Thanks @js2me! - rich typings and data for parsed route raw data

v13.6.8

Patch Changes

• 8414b3c Thanks @js2me! - Fix extracted response/error type names colliding with existing schemas. Add tests.

v13.6.7

Patch Changes

• 4603a7e Thanks @js2me! - fixed bug #1668 (random of type names)

v13.6.6

Patch Changes

• d57ecdc Thanks @js2me! - fix bug #1433 (incorrect yaml multiline files)

v13.6.5

Patch Changes

• bd68761 Thanks @js2me! - fixed bug linked with unused query param (bug #1433 , 1 point)