Skip to content

Accept readOnly fields sent back in a request - #9

Merged
inkly merged 1 commit into
mainfrom
fix/readonly-in-requests
Sep 25, 2026
Merged

inkly merged 1 commit into
mainfrom
fix/readonly-in-requests

Conversation

@inkly

@inkly inkly commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

Saving backup schedules failed with 'readOnly property last_run in request' once a schedule had run: the dashboard sends the list back as it read it, and kin-openapi v0.149 refuses readOnly properties in requests by default. The handlers already ignore those fields, so the validator now skips that check (ExcludeReadOnlyValidations). For ReCasaOS/CasaOS#7.

The dashboard edits what it read and sends it back whole: a backup
schedule carries its last_run. The handlers ignore such fields and keep
their own, but kin-openapi refuses them by default since the version this
project moved to, so saving any schedule once one had run failed with
"readOnly property last_run in request" (ReCasaOS/CasaOS#7). The request
validator now leaves readOnly fields to the handlers.
@inkly
inkly merged commit 4f561cf into main Sep 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant