Add content_private_body notification field#889
Merged
Conversation
Collaborator
cdesquilbet-dila
left a comment
cdesquilbet-dila
left a comment
There was a problem hiding this comment.
Est-ce qu'il y a un dév particulier à faire pour ne pas que content_private_body soit passé à Firebase ?
Collaborator
Author
Les notifications push (envoyées à Firebase) sont créées et envoyées par le fichier push.py. Les données envoyées sont construites ici, et on peut voir qu'il n'y a pas le C'est ensuite vérifié dans les tests à cet endroit |
Collaborator
|
Parfait, merci ! |
cdesquilbet-dila
approved these changes
May 21, 2026
magopian
force-pushed
the
875-add-content_private_body-notification-field
branch
from
24a6b77 to
b8e1bc9
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #875