[MGNLUI-2658] As a developer, I can confidently reuse content views across various data sources Created: 07/Feb/14  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: workbench
Affects Version/s: 5.2
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Mikaël Geljić Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
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)

 Description   

Currently ContentViews and ContentPresenter APIs are tightly coupled to concrete JCR containers and - and even JCR adapters or util in the case of tree view's inplace editing.

Responsibilities and APIs should be reconsidered between what belongs to workbench vs. what belongs to content presenters, so that config-wise, there would be almost no difference between registering e.g. tree view for a JCR workbench or Filesystem workbench.

Ideally we can do something like ContentPresenter.start(ContentPresenterDefinition, Container containerDataSource).

More info in linked concept page (Level 4)


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