Page MenuHomePhabricator

Remove counts from home navigation

Authored by chad on Jan 20 2017, 9:28 PM.
Referenced Files
F13440588: D17238.id41460.diff
Fri, Jul 12, 7:28 AM
F13438277: D17238.id41460.diff
Thu, Jul 11, 8:30 PM
F13412744: D17238.diff
Sun, Jul 7, 3:40 AM
F13393612: D17238.id41457.diff
Wed, Jul 3, 12:54 AM
Wed, Jul 3, 12:54 AM
F13393609: D17238.id41456.diff
Wed, Jul 3, 12:54 AM
F13393558: D17238.diff
Wed, Jul 3, 12:39 AM
F13386115: D17238.id41457.diff
Mon, Jul 1, 4:34 AM



Ref T12136. This just yanks the band-aid off. Fundamentally these were useful well before Dashboards and advanced bucketing, but not so much any more. They also have some performance hit.

Test Plan

Add some tasks and diffs onto a new instance, see there is no count on the home menu bar.

Diff Detail

rP Phabricator
Lint Not Applicable
Tests Not Applicable

Event Timeline

I think we can get rid of a lot more stuff, like DifferentialApplication->loadNeedAttentionRevisions(), PhabricatorApplication->loadStatus() and callsites, the entire PhabricatorApplicationStatusView class, the stuff in People, Phrequent, Maniphest and Flags, probably some strings in USEnglishTranslation if you want to get ambitious, and the MAX_STATUS_ITEMS constant. Like seven million lines of code.

This revision now requires changes to proceed.Jan 20 2017, 11:26 PM

seems like we could easily integrate this into MenuItem. I didn't know about loadStatus

chad edited edge metadata.
  • remove php code

Maybe even some CSS!

I'll leave CSS for another diff in case we have to resurrect this code after the menu swap.


We could definitely integrate this into MenuItem (at least, if Home is staying wide? Maybe not if it's collapsing like Projects?) but ideally maybe no one notices or misses this stuff.

If we do ultimately put it back I want to try to put some proper caching behind it -- the cost is really disproportionate to the value, especially since 80% of the value is probably "is there a count or not" for users who find it valuable?

Maybe hold this for the release cut just in case? Although I wanted to try to get some more stuff in so I dunno what's going on there yet.

This revision is now accepted and ready to land.Jan 21 2017, 12:07 AM

In pretty much all cases, I’d rather put time into fixing dashboards or
building Nuance, etc, if the count behind something is important.

Yes, I plan to hopefully have one wide menu for projects/home and roll them
out together.

Yeah, completely agreed.

Also I think I'm going to churn on some more stuff before cutting the release so just go ahead and kick this in, should have plenty of time to soak. I was just vaguely thinking I'd be cutting in like 15 minutes but I'm not going to try to rush it.

one wide menu for projects/home


Also I think I'm going to churn on some more stuff before cutting the release

uh or I'll just do it now


This revision was automatically updated to reflect the committed changes.