openapi3: update date schema formats to not match months or days of '00' #1042
Conversation
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
|
This PR addresses issue #1043 |
ccoVeille
reviewed
Dec 11, 2024
ccoVeille
reviewed
Dec 11, 2024
ccoVeille
approved these changes
Dec 11, 2024
|
@fenollp I'm not sure what the merge process is, but it looks like you're pretty involved in it. Mind taking a look? :) |
fenollp
changed the title
|
Thanks! |
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.
Does what it says on the tin, per the permissible value range for
date-monthanddate-mdayof section 5.6 of the RFC3339 standardEDIT TO ADD:
Also updates hours, minutes, and seconds to be bounded from
00-23,00-59, and00-60respectively (the60is for the leap second).