-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add isReplyAllowed field to notification entity [WPB-7425] 🍒 #2871
feat: Add isReplyAllowed field to notification entity [WPB-7425] 🍒 #2871
Conversation
import com.wire.kalium.logic.functional.map | ||
<<<<<<< HEAD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.
…d_to_notification_entity-cherry-pick
Datadog ReportBranch report: ✅ 0 Failed, 2968 Passed, 105 Skipped, 12.24s Total Time |
Quality Gate passedIssues Measures |
This PR was automatically cherry-picked based on the following PR:
Original PR description:
What's new in this PR?
Issues
Need to remove option "Reply" from the notifications in conversations that has Degraded verification status.
Causes (Optional)
Wasn't implemented yet.
Solutions
Update DB-query to get also
Conversation.degradedConversationNotified
while getting notifications and use it asisReplyAllowed
flag in creating OS-notifications.