feat: add event history id to answer submissions (M2-8481) #944
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
ChaconC
changed the title
farmerpaul
approved these changes
Feb 26, 2025
|
@ChaconC ChildMindInstitute/mindlogger-backend-refactor#1754 should be merged first to prevent breaking answer submission in the app |
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
Important
For the answer submission to be accepted by the BE, it requires running it with this branch checked out: ChildMindInstitute/mindlogger-backend-refactor#1754
🔗 Jira Ticket M2-8481
Adds
eventHistoryIdto new submissions, making sure to use the existing queue service.🪤 Peer Testing
eventHistoryIdis included in the payloadencryptedDatapayload inAnswersUploadService.uploadAnswersor by ensuringevent_history_idis saved in the new answer directly in the database.