fix: remove readOnly fields from body schema parsing before Zod generation #1625
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.
Status
READY
Description
close #1548
parseBodyAndResponse
to applyremoveReadOnlyProperties
when parsing the body, ensuring that readOnly fields are excluded before generating the Zod schema.Related PRs
List related PRs against other branches:
Todos
Steps to Test or Reproduce
Set up the following files and verify that the generated body schema does not include any properties that have readOnly set to true.
orval.config.js
petstore.yaml
the output in my environment is as follows:
before the change
after the change