You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Tests for the changes have been added/updated (for bug fixes/features)
Docs have been added/updated (for bug fixes/features)
Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
Self-reviewed and ran all changes on a local instance (for bug fixes/features)
Change has impacts in these area(s)
(check all that apply)
Product design
Backend (Database)
Backend (API)
Frontend
Describe the reason for change
The auto-save feature for annotations currently triggers a draft save request 5 seconds after annotation begins. In our Selenium tests, this timing issue sometimes causes both the draft and annotation submission requests to be sent simultaneously. This can result in duplicated draft and annotation being displayed in the quick view for users.
What does this fix?
This change implements a queue system to manage the timing of draft saves and annotation submissions. The annotation submission now waits until the draft save request is completed before proceeding. This ensures that the backend processes these requests sequentially, preventing duplication issues.
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.
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
The auto-save feature for annotations currently triggers a draft save request 5 seconds after annotation begins. In our Selenium tests, this timing issue sometimes causes both the draft and annotation submission requests to be sent simultaneously. This can result in duplicated draft and annotation being displayed in the quick view for users.
What does this fix?
This change implements a queue system to manage the timing of draft saves and annotation submissions. The annotation submission now waits until the draft save request is completed before proceeding. This ensures that the backend processes these requests sequentially, preventing duplication issues.