Update submission in s3 even after review state is updated #1379
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.
What type of PR is this? (check all applicable)
Related Issue
Describe this PR
Previously, submissions were updated to S3 by checking the last submission date, but if someone changes the review state, it won't change the date due to which submission wasn't updated. This PR adds the review state to the submission meta json in s3, which is compared with the review state obtained from odkcentral. Those obtained lists of review states are converted into hash strings so that they can be compared easily without going through every element of the list.
Checklist before requesting a review
[optional] What gif best describes this PR or how it makes you feel?