[JN-1681] make created at duplicates more obvious + fix lots of issues with translate script #1617
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
connorlbark
changed the title
|
devonbush
approved these changes
May 13, 2025
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.
DESCRIPTION (include screenshots, and mobile screenshots for participant UX)
Because our import system will attempt to "merge" tasks together that have the same createdAt, we have to be really careful... if they're a minute apart it's ok, and since the lowest resoluation we have on import is a minute, we just need to make sure we don't have duplicates. If a duplicate exists, they'll be merged together and it's not clear which one would "win".
I thought about making an auto-solution, but it only occurs about 30-40 times across all participants in A-T prod. I think it's easier to just manually clean it up - i.e. edit them to sure that no longitudinal responses have the same timestamp
TO TEST: (simple manual steps for confirming core behavior -- used for pre-release checks)