-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[PM-10600] Push notification with full notification center content #5086
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5086 +/- ##
=======================================
Coverage 44.43% 44.43%
=======================================
Files 1500 1500
Lines 69521 69546 +25
Branches 6262 6262
=======================================
+ Hits 30890 30905 +15
- Misses 37304 37314 +10
Partials 1327 1327 ☔ View full report in Codecov by Sentry. |
Great job, no security vulnerabilities found in this Pull Request |
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.
Makes sense to me. KM team for full review.
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.
LGTM
test/Core.Test/NotificationHub/NotificationHubPushNotificationServiceTests.cs
Show resolved
Hide resolved
…ifications We only register devices for organization push notifications when the organization is being created. This does not work, since we have a use case (Notification Center) of delivering notifications to all users of organization. This fixes it, by adding the organization id tag when device registers for push notifications.
Fixed IFeatureService substitute mocking for Android tests. Added user part of organization test with organizationId tags expectation.
…ter merge conflict
9a06ab7
to
997165d
Compare
Notification Center push notification now includes all the fields.
997165d
to
02e45c3
Compare
I had to rebase and force push on top of |
The base branch was changed.
# Conflicts: # src/Core/Models/PushNotification.cs # src/Core/NotificationCenter/Commands/CreateNotificationCommand.cs # src/Core/NotificationHub/NotificationHubPushNotificationService.cs # src/Core/Platform/Push/Services/AzureQueuePushNotificationService.cs # src/Core/Platform/Push/Services/IPushNotificationService.cs # src/Core/Platform/Push/Services/MultiServicePushNotificationService.cs # src/Core/Platform/Push/Services/NoopPushNotificationService.cs # src/Core/Platform/Push/Services/NotificationsApiPushNotificationService.cs # src/Core/Platform/Push/Services/RelayPushNotificationService.cs # src/Notifications/HubHelpers.cs # test/Core.Test/NotificationCenter/Commands/CreateNotificationCommandTest.cs # test/Core.Test/NotificationHub/NotificationHubPushNotificationServiceTests.cs # test/Core.Test/Platform/Push/Services/AzureQueuePushNotificationServiceTests.cs # test/Core.Test/Platform/Push/Services/MultiServicePushNotificationServiceTests.cs
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-10600
This is Part 2.
See Part 1: #4923
See Part 3: #5057
📔 Objective
Notification Center push notification now includes all the fields.
The push notification have a limit of 4KB for payload (limitation of Azure Notification Hub, FCM and APNS). For notification center push notification, only
Body
field needs to have a max length, since other fields have deterministic max length. No other push notifications are affected.To fix this, a separate PR will follow once the API PR is merged #4852 that will have the max length of 3000 on the
Body
field in the request and optionally in db column too.📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes