Conversation
|
🪓 PR closed, deleted preview. |
…participant-completion-end-submission-refactor
JackWilb
deleted the
latency-safe-participant-completion-end-submission-refactor
branch
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.
Does this PR close any open issues?
Closes #
Give a longer description of what this PR addresses and why it's needed
This PR fixes two related issues in participant finalization.
First, it moves completion status to the source of truth in sequence assignments instead of storing it on ParticipantData. Analysis, downloads, and table views now use a ParticipantDataWithStatus shape so completed/in-progress state reflects the realtime assignment status consistently.
Second, it hardens the study end flow. The end screen now keeps the app in a final-submission state while completion is being finalized, preserves the unload warning during that window, and removes the end-card flicker caused by locally refetching dataCollectionEnabled and treating its initial value as “disabled.” The end view now uses the already-loaded store mode instead.
Provide pictures/videos of the behavior before and after these changes (optional)
Are there any additional TODOs before this PR is ready to go?
TODOs: