feat: remove override.coerceTypes option (BREAKING CHANGE) #2484
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.
fix #2478
Summary
Remove the deprecated
override.coerceTypesoption. Users should useoverride.zod.coerceinstead.The
override.coerceTypesoption was deprecated in favor of the more flexibleoverride.zod.coerceconfiguration, which provides granular control over coercion for different parameter types (query, body, response, etc.). Removing the deprecated option simplifies the codebase and encourages users to adopt the better alternative.export default { petstore: { output: { override: { - coerceTypes: true, + zod: { + coerce: { + query: true, + }, + }, }, }, }, };