v4.3.0

🐣 Minor changes

• In many areas, changed out any with unknown (#769). See #554 for more explanation / context

🐛 Bugfixes

• An old bug is now gone! openapi-typescript would incorrectly generate { [key: string]: unknown } for a type when it may have been a string or number. Now it will generate a more generic unknown type, unless it knows it’s dealing with an object for sure.

v4.2.0

✨ New Features

• Reference arbitrary data on generated types via the properties key by @Peteck (#626)

v4.1.1

🐛 Bugfixes

• Fixes the remote schema URL cache being too long-lived by @mbelsky (#708)

v4.1.0

✨ New features

• New --headersObject and --headers CLI flags by @ericzorn93 (#764)

🐛 Bugfixes

• "type": "file" no longer generates unexpected results (#766)

v4.0.2

🐛 Bugfixes

• Loading in-memory schemas through the JS API resulted in broken $refs (#689)

v4.0.1

🐛 Bugfixes

• Fixes properties + anyOf with only required properties by @gr2m (#643)

v4.0.0

✨ New Features

• Now supports remote references ($ref: "remote.yaml#/components/schemas/User) 🎉 (#602)!

⚠️ Breaking Changes

• The Node.js API is now promise-based, and can no longer be run synchronously (a necessity because resolving remote schemas can never be synchronous). Other than that, there are no other breaking changes. CLI users are unaffected, and the types generated are backwards-compatible with previous versions.

v3.4.1

🐛 Bugfixes

• v3.4.0 would accidentally generate empty folders alongside single-file schemas. This fixes that (#633).

v3.4.0

✨ New Features

• Features glob support thanks to @sharmarajdaksh (#615)

🐥 Minor changes

• Reverts #613 and adds a --default-non-nullable flag (#631)

v3.3.1

🐛 Bugfixes

• Schema objects that have a default: property shouldn’t be marked as nullable (#613)