Merged
Conversation
niksirbi
approved these changes
Jul 30, 2025
Member
niksirbi
left a comment
niksirbi
left a comment
There was a problem hiding this comment.
I've added one suggestion for combining the 3 bullet points into 1.
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
3 participants
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.
Related to #31 #74 this PR enforces that any date / time / datetimes are in ISO8601 format (previously this was suggested). It also makes it clearer that using
date-,time-ordatetime-keys is recommended but not mandated (combined with #75 this would allow their use assub-orses-labels as discussed in #74 @glopesdev).This PR changes the specification and requires no tests or further documentation.