Page MenuHomePhabricator

[Redesign] Put all ApplicationSearch results in an ObjectBox
ClosedPublic

Authored by chad on May 24 2015, 2:41 PM.
Tags
None
Referenced Files
F13089554: D12989.diff
Thu, Apr 25, 1:53 AM
Unknown Object (File)
Fri, Apr 12, 6:57 AM
Unknown Object (File)
Sun, Apr 7, 8:13 PM
Unknown Object (File)
Mar 5 2024, 10:42 AM
Unknown Object (File)
Feb 13 2024, 8:21 AM
Unknown Object (File)
Feb 7 2024, 11:53 AM
Unknown Object (File)
Feb 3 2024, 11:49 AM
Unknown Object (File)
Feb 3 2024, 4:11 AM
Subscribers

Details

Summary

Ref T8099. In most cases we return either an ObjectList or AphrontTable, and can pretty up the UI in ApplicationSearch. There are a few edge cases, like PeopleUserLog, that can be cleanup up individually in the future, but look fine for now.
Also added 'setNotice' for AphrontTable for a few cases where we want to convey addtional information.

TODO: Seems we always pass a Pager Object, which tries to get displayed, I'll redesign that interaction in the future, probably by passing the Pager to the ObjectBox

Test Plan

Went throught most/all ApplicationSearch panels I could find, even edge cases look better.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

chad retitled this revision from to [Redesign] Put all ApplicationSearch results in an ObjectBox.
chad updated this object.
chad edited the test plan for this revision. (Show Details)
chad added reviewers: epriestley, btrahan.
epriestley edited edge metadata.
This revision is now accepted and ready to land.May 24 2015, 2:45 PM

I'm curious what's the right "longterm" solution here. Right now ApplicationSearch Queries *usually* return a List or Table, but sometimes other content and sometimes they modified the Header before sending. DashboardEngine does something similar. Should we maybe have a Header at the Query level as optional get sent up to ApplicationSearch then modified there? Sort of like DashboardPanels?

I'd have to spend some time looking at it and collecting the edge cases. I'd guess that we maybe require them to return some SearchResultListView sort of thing, and that's basically a thin wrapper around a header + form + results + pager, most of which gets filled in by default in most cases.

Pulling the pager/header/etc out separately might be another approach, but I'd guess it's messier overall.

This revision was automatically updated to reflect the committed changes.