[MGNLUI-235] Apps: Adapt all content apps to not implement their own implementation of the views Created: 27/Nov/12  Updated: 28/Jun/13  Resolved: 28/Jun/13

Status: Closed
Project: Magnolia UI
Component/s: content app
Affects Version/s: None
Fix Version/s: 5.0

Type: Bug Priority: Major
Reporter: Tobias Mattsson Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: apiteam, framework
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-230 Simplify SubAppViews Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

UPDATE: This is implemented for the contacts app. All other content apps should be adapted accordingly.

Most implementations of WorkbenchSubAppView are simple implementations that add no logic of their own. It would make the content app classes even easier to use if adding your own such implementation was optional.

See for instance:

  • info.magnolia.ui.app.security.view.UsersViewImpl
  • info.magnolia.ui.app.pages.main.PagesMainViewImpl
  • info.magnolia.ui.app.contacts.item.ContactsItemViewImpl
  • info.magnolia.ui.app.contacts.ContactsViewImpl
  • info.magnolia.ui.app.security.view.GroupsViewImpl
  • info.magnolia.ui.app.security.view.RolesViewImpl


 Comments   
Comment by Tobias Mattsson [ 27/Nov/12 ]

Jozef have made progress towards this in the security app. Its views have been replaced by a single ViewImpl.

Generated at Mon Feb 12 08:34:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.