feat: output OpenAPI v3 instead of v3.1 #536
Conversation
bitgopatmcl
force-pushed
the
use-openapi-v3
branch
from
cd436cc to
0566561
Compare
|
Rebased to fix semantic merge conflict with #537 |
|
🎉 This PR is included in version @api-ts/openapi-generator@2.5.0 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/typed-express-router@1.1.1 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/express-wrapper@1.0.21 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/superagent-wrapper@1.1.12 🎉 The release is available on npm package (@latest dist-tag) Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version @api-ts/io-ts-http@2.4.1-beta.1 🎉 The release is available on Your semantic-release bot 📦🚀 |
2 participants
It appears that a lot of tooling does not support OpenAPI v3.1, so this changes
openapi-generatorto output OpenAPI v3 for broader compatibility. The largest change is with explicitnull-typed properties, since OpenAPI does not have anullprimitive type. As a workaround, I have it emit anullabletype with an emptyenum, which should mean the only possible value for that type isnull, but I'm guessing a lot of tooling conflates "nullable" with "optional" and we might need to handle this in the future.