feat: add exportAllNamedSchemas option to allow exporting duplicate schemas with different names. #268
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.
This PR provides a new option,
exportAllNamedSchemas
, to override that behavior and export all named schemas even if they are the same type.The default behavior was causing the same schema name to be used in multiple places and the semantics did not make sense.
Example:
This portion of schema with a complexity of 0 would result in a single
username: z.string()
schema set to bothusername
andpassword
query parameters, as well as any other parameters that areschema.type: string
Result: