test: Pin date-time format precision tolerance#102
Merged
Conversation
The OpenAPI 'date-time' string format delegates to OffsetDateTime.parse, which already accepts everything from second precision through nanosecond precision (and either Z or numeric offset). Pin that behaviour so we can keep emitting Java's natural toString() form on responses without fear of clients sending higher-precision timestamps back to us.
thced
force-pushed
the
fix/temporal-precision
branch
from
06b60b9 to
3c9b3ed
Compare
thced
changed the title
|
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
1 participant
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.
Java's OffsetDateTime/Instant/ZonedDateTime/LocalDateTime/LocalTime toString() omits seconds and fractional digits when zero, producing inconsistent serialised forms (e.g. "20:00Z" vs "20:00:00.123456Z"). Encode through a DateTimeFormatter that always writes six-digit (microsecond) fractional precision. Decoding remains permissive via each type's ISO parser.