Accept milliseconds in request date field#232
Merged
Conversation
aracho1
force-pushed
the
ac/update-date-time-parser-new
branch
from
July 17, 2026 12:54
e55b765 to
e9fccc4
Compare
aracho1
changed the title
aracho1
changed the title
vlbee
approved these changes
Jul 21, 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
2 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.
What does this change?
e.g.2026-07-17T10:15:30.123Z) which is valid ISO-8601 but our parser. is too strict at the moment so will reject it.outputFormatter) to ensure consistency in our output in API response and DB writesHow has this change been tested?
Deployed to CODE and tested on Android emulator
Test request body (date/time with milliseconds)
Before the current change
400 Bad Request
After the current change
200 (with the millis seconds dropped)