Page MenuHomePhabricator

Conpherence - update the "unread" count in notifications panel aggressively
ClosedPublic

Authored by btrahan on Mar 17 2015, 8:34 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 7:38 PM
Unknown Object (File)
Thu, Dec 12, 6:08 AM
Unknown Object (File)
Thu, Dec 12, 3:49 AM
Unknown Object (File)
Wed, Dec 11, 9:38 PM
Unknown Object (File)
Wed, Dec 11, 2:14 PM
Unknown Object (File)
Mon, Dec 9, 11:40 AM
Unknown Object (File)
Fri, Dec 6, 7:02 AM
Unknown Object (File)
Fri, Nov 29, 8:43 PM
Subscribers

Details

Summary

Fixes T7561. Basically everytime we load some transactions in the thread manager, kick off an async thread to update the notification panel.

Should I consolidate this little bit of code into something like this._handleTransactionResponse(r)... ? I just want to keep the JS clear for other engineers and I wasn't sure if that was hiding a bit too much detail.

Test Plan

user a opened durable column. user b sent user a a few messages. reloaded user a page and noted the "N" count became N-1 as the message loaded. Switched messages and saw N-2, N-3, etc as I loaded up the messages.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

btrahan retitled this revision from to Conpherence - update the "unread" count in notifications panel aggressively.
btrahan updated this object.
btrahan edited the test plan for this revision. (Show Details)
btrahan added reviewers: epriestley, chad.
epriestley edited edge metadata.

It might also make sense to piggyback this stuff on the response at some point (so when you query for messages, you also get the menu state back) but this diff is pretty simple/clean/reasonable until we have a stronger motivation for that.

This revision is now accepted and ready to land.Mar 17 2015, 8:36 PM
This revision was automatically updated to reflect the committed changes.