Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-2658

As a developer, I can confidently reuse content views across various data sources

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Open
    • Priority: Neutral
    • Resolution: Unresolved
    • Affects Version/s: 5.2
    • Fix Version/s: None
    • Component/s: workbench
    • Labels:
      None

      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)

        Checklists

        Acceptance criteria

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                mgeljic Mikaël Geljić
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    Checklists

                    DoD