Page MenuHomePhabricator

Utilise subscription from ThickMemberInfo when building a notif
Needs ReviewPublic

Authored by marcin on Fri, Jun 21, 4:09 AM.
Tags
None
Referenced Files
F2169242: D12539.id41716.diff
Tue, Jul 2, 10:49 AM
F2165329: D12539.id.diff
Tue, Jul 2, 1:32 AM
Unknown Object (File)
Sun, Jun 30, 9:34 PM
Unknown Object (File)
Sun, Jun 30, 2:41 PM
Unknown Object (File)
Thu, Jun 27, 12:50 PM
Unknown Object (File)
Wed, Jun 26, 5:03 PM
Unknown Object (File)
Wed, Jun 26, 1:46 PM
Unknown Object (File)
Tue, Jun 25, 4:43 PM
Subscribers

Details

Reviewers
kamil
tomek
Summary

This differential extracts a common logic that uses thread subscription, user role and mentioning to decide whether to send a notif. Moreover this logic is used in the client-send code.

Test Plan
  1. Test that chat muting and user mentioning (also for ENS users) works on the keyserver from the notif perspective.
  2. To test the client, apply patch from D12477 and then:
    1. Without any changes there should be no notif payloads generated.
    2. Play around with hardcoding different configurations of thread subscriptions and examine content of generated notifs.

Diff Detail

Repository
rCOMM Comm
Branch
marcin/eng-8410
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

Fix a bug: notifsAllowed returned variable was assigned to wrong condition

lib/push/utils.js
168–173 ↗(On Diff #41716)

This is too many parameters. Please replace with an object param, and keep this in mind going forward