Page MenuHomePhabricator

Allow Portals to be edited, and improve empty/blank states
ClosedPublic

Authored by epriestley on Mar 29 2019, 10:13 PM.
Tags
None
Referenced Files
F15490759: D20349.id48603.diff
Fri, Apr 11, 8:22 PM
F15489416: D20349.id48603.diff
Fri, Apr 11, 8:56 AM
F15489329: D20349.id48565.diff
Fri, Apr 11, 7:58 AM
F15488145: D20349.id.diff
Thu, Apr 10, 7:50 PM
F15483775: D20349.diff
Wed, Apr 9, 2:20 PM
F15470357: D20349.id48603.diff
Fri, Apr 4, 9:39 PM
F15469377: D20349.diff
Fri, Apr 4, 12:32 PM
F15445833: D20349.id48603.diff
Thu, Mar 27, 4:11 PM
Subscribers
None

Details

Summary

Depends on D20348. Ref T13275. Portals are mostly just a "ProfileMenuEngine" menu, and that code is already relatively modular/flexible, so set that up to start with.

The stuff it gets wrong right now is mostly around empty/no-permission states, since the original use cases (project menus) didn't have any of these states: it's not possible to have a project menu with no content.

Let the engine render an "empty" state (when there are no items that can render a content page) and try to make some of the empty behavior a little more user-friendly.

This mostly makes portals work, more or less.

Test Plan

Screen Shot 2019-03-29 at 3.03.39 PM.png (910×1 px, 288 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable