[zod-nestjs] Recursively convert to OpenAPI 3.0 specification #185
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi and sorry I did not fix this right away in #182.
In my project I have a somewhat advanced structure of Zod validation schemes with nested objects and arrays. So far, we only convert OpenAPI 3.1 back to OpenAPI 3.0 for objects and only on the root level, e. g. the
properties
object. However, schema objects can incorporate other schema objects in a bunch of other places, for exampleanyOf
oritems
for arrays,This PR addresses this problem by recursively converting
zod-openapi
's OpenAPI 3.1 object back to OpenAPI 3.0 for NestJS.