[MGNLUI-1556] ContentViews should not be identified with an enum Created: 04/Jun/13  Updated: 16/Aug/13  Resolved: 08/Aug/13

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: 5.0
Fix Version/s: 5.1

Type: Bug Priority: Major
Reporter: Tobias Mattsson Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: apiteam
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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
Date of First Response:

 Description   

We need to support adding new ContentViews, so we cannot have an enum with a fixed number of options.

It needs to be changed to a simple string name.



 Comments   
Comment by Mikaël Geljić [ 08/Aug/13 ]

View types that have specific handling (tree, list, search) are now defined as VIEW_TYPE constants in their respective ContentPresenterDefinitions.

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