Switches over to new property UI boxes, splits core and apps into separate pages. Move Versions into "All Settings". I think there is some docs I likely need to update here as well.
Details
- Reviewers
epriestley - Commits
- rP15ed2b936c37: Update Config Application UI
Click on each item in the sidebar, see new headers.
Diff Detail
- Repository
- rP Phabricator
- Branch
- config2 (branched from master)
- Lint
Lint Passed - Unit
Tests Passed - Build Status
Buildable 13387 Build 17183: Run Core Tests Build 17182: arc lint + arc unit
Event Timeline
I'm hesitant about moving "Versions" into "All Settings":
- We describe how to get this information in Providing Version Information, and changing it will confuse users filing reports more than they're already confused (the instructions won't work any more for users who aren't up to date if we make this change).
- Users have a hard time reporting this information consistently even though it says "Version" right now. It's unintuitive to me that "Version" is in "All Settings"; I would never guess that I needed to click that even if I knew that version information was in Config somewhere.
- After T5055, I expect this page to show more information (versions of all installed extensions, plus information about them), none of which will be related to settings.
Of all the stuff here, I generally think "Versions" is one of the most important items? What's the goal in merging it?
If you just want to clean up the number of items here, I'd rather get rid of other stuff -- maybe we can divide this application into multiple applications ("Config" vs "Setup"? -- although I think that also risks confusion) or put a dashboard with bigger categories here as the landing page and then dump you into smaller sub-sections?
The code is fine, this just seems like a small step backward in getting good bug reports and I'm not sure what we gain by merging the sections.
I mostly want to move "Versions" up from under the fold. I was tempted to go further and have it just at the top of the /, so it was always available when you land in Config? Alternatively I can just make it a Controller instead of a Module and place it up under "All Settings".
Alternatively I can just make it a Controller instead of a Module and place it up under "All Settings".
Ah! That sounds good to me. I think it'll get expanded in T5055 anyway and probably want to become a controller at that point regardless.