fix(database): standardize achievedAt to ISO-8601 and harden date parsing#81
Merged
Merged
Conversation
…sing Signed-off-by: BoxBoxJason <contact@boxboxjason.dev>
BoxBoxJason
added
bug
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.
This PR standardizes time format for achievedAt across the codebase.
There was currently a conflict between the default SQL
CURRENT_TIMESTAMPand the one we arbitrarely decided on.This aligns them by using only javascript one, and for backwards compatibility, the time decoding function has been adapted to support both.
Fixes #66