feat(decrypted_notify): adding always_raw
for the client registration
#279
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
This PR adds
always_raw
field to the clients database table and to the client register endpoint as an optional field with thefalse
as default to follow the specs for the decrypted notifications.Related to #278
How Has This Been Tested?
Updated functional tests.
Review stack 🏗️
1 - Adding always_raw for the client registration #279 <-
2 - Update message payload and pass raw message #281
Due Diligence