fix round seconds formatting in JobResponseMapper #375
Conversation
This file contains 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
|
|
codewithbear
force-pushed
the
fix-list-jobs-public-api-date
branch
2 times, most recently
from
49a9b68 to
c7d82f7
Compare
codewithbear
force-pushed
the
fix-list-jobs-public-api-date
branch
from
c7d82f7 to
6e0f520
Compare
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.
What
Currently if a job has been started (or updated) at the start of minute (seconds = 0) the formatting omits seconds so in the public api it would look like this
How
Using DateTimeFormatter to make sure to always include seconds
Can this PR be safely reverted and rolled back?