Repository navigation
Document ISO 8601 dates of calendar rules in the REST API spec - #192
Merged
Merged
Conversation
The OpenAPI schema of CalendarRuleItem only declared start and end as date-time strings. Describe what the handler accepts: start is an ISO 8601 date-time taken as UTC when it has no offset, integer timestamps are rejected, and end is a calendar day kept as sent (not converted to UTC).
janpenitent
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The OpenAPI schema of CalendarRuleItem only declared start and end as date-time strings. Describe what the handler accepts: start is an ISO 8601 date-time taken as UTC when it has no offset, integer timestamps are rejected, and end is a calendar day kept as sent (not converted to UTC).