-
Notifications
You must be signed in to change notification settings - Fork 216
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
🟢 Apply (polls) push rules client side for encrypted rooms #1714
🟢 Apply (polls) push rules client side for encrypted rooms #1714
Conversation
Codecov ReportBase: 17.52% // Head: 17.51% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1714 +/- ##
===========================================
- Coverage 17.52% 17.51% -0.01%
===========================================
Files 612 612
Lines 95983 95988 +5
Branches 40286 40289 +3
===========================================
- Hits 16823 16817 -6
- Misses 78649 78660 +11
Partials 511 511
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
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
@@ -101,6 +101,9 @@ import Foundation | |||
public func pushRule(matching event: MXEvent, | |||
roomState: MXRoomState, | |||
currentUserDisplayName: String?) -> MXPushRule? { | |||
// getting the uncrypted event if present or fallback |
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.
// getting the uncrypted event if present or fallback | |
// getting the unencrypted event if present or fallback |
…apply_poll_push_rules_encrypted-rooms
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!
push rules for an event was broken because it was reading the encrypted one.
Now if present the clear event, the proper rule id is matching properly.
It was also missing the pushRulesManager's handle account data in the updateBackgroundServiceStoresIfNeeded, that way it was not synchronised and a reboot of the app was needed in order to fetch the proper push rules