aed5735620
Bind a single listener to keychange events from the storage interface, which then looks up relevant conversations and adds notices to them, with tests. Previously we would need to instantiate a conversation model in order to start listening to its key change events. In practice this usually happens at startup but we shouldn't rely on it, and it incurs higher overhead since it creates a different listener for each conversation. // FREEBIE |
||
|---|---|---|
| .. | ||
| blockedNumbers.js | ||
| conversations.js | ||
| messages.js | ||