We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shema entity example
LegalEntity: type: object properties: id: type: string format: uuid readOnly: true created_at: type: string format: date-time readOnly: true updated_at: type: string format: date-time readOnly: true name: type: string maxLength: 255 required: - created_at - id - name - updated_at
Generated zod schema for create body have all the fields that marked as readOnly
export const v1OrgstructureLegalEntitiesCreateBody = zod.object({ "id": zod.string().uuid(), "created_at": zod.string().datetime(), "updated_at": zod.string().datetime(), "name": zod.string().max(v1OrgstructureLegalEntitiesCreateBodyNameMax), })
readonly fields appears only in get-like actions and responses
so it means that CreateBody expected to be
export const v1OrgstructureLegalEntitiesCreateBody = zod.object({ "name": zod.string().max(v1OrgstructureLegalEntitiesCreateBodyNameMax), })
"orval": "^6.31.0", "zod": "^3.23.8"
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
What are the steps to reproduce this issue?
Shema entity example
What happens?
Generated zod schema for create body have all the fields that marked as readOnly
What were you expecting to happen?
readonly fields appears only in get-like actions and responses
so it means that CreateBody expected to be
What versions are you using?
"orval": "^6.31.0",
"zod": "^3.23.8"
The text was updated successfully, but these errors were encountered: