feat(client): add EncryptionService to validate encrypt submission responses #2436
+337
−3
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.
Problem
Storage mode submissions saved to the database cannot be updated due to end-to-end encryption. This means that submissions saved in the wrong format can be difficult or impossible to salvage.
This PR introduces
EncryptionService
which contains a validation function, enforcing the shape of the submission response. Using this service with the present AngularJS code in production and subsequently reusing it with React can assure us that it the encryption is being performed correctly in the new frontend.To implement the above service, various field response zod schema constants are created in the new rooted
/shared
folder and used for the validation.Closes #2209
Solution
Breaking Changes
Features:
Improvements:
Tests
Manual tests