Context
With the "search-X" initiative - content-apps change slightly - this must be reflected by the ContentApp page object (PO).
The Search-X is meant for 6.3 webapps only.
"Search-X enabled"
"Search-X" improves the search-experience - and it is changing couple of things.
When enabled ...
- Some filters disappear.
- End-User cannot swap between tree- and list-view
- App starts with the tree-view.
- Search results are displayed in list-view
Some of these things are configurable, but not for the "end-user" - and that's how it is atm.
Which apps are "Search-X enabled"?
Currently only pages and assets. Others may follow in phase-2 or phase-3 of the search-X-initiative.
Required changes on the ContentApp PO, related POs and possibly on tests
ContentApp
- can differentiate between "normal" and "search-x-enabled"
- if "search-x-enabled"
- cannot use the #setActiveView / #setActiveView has no effect
Grid
- Grid related methods all still work fine
- provides #getViewType
- to also (re-)use it in ChooserDialog
Toolbar
- #getActiveView -> move to Grid
- deprecate setActiveView
Tests
ContentAppTest, ContentAppFilterTest, ContentAppGridTest, ChooserDialogTest work fine.
When disabling tests, create tickets to -re-enable.
Rename former NewContentAppTest to ContentAppGridTest.
Difficulty
This can be tested only against 6.3-test-webapp
|