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

Resurrect the DefaultAvailabilityChecker and use that one in pulse-context

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Obsolete
    • Neutral
    • 5.4.x
    • None
    • None
    • None

    Description

      Now, that we use action availability, we inject AvailabilityCheckerImpl which in turn injects the DefaultContentConnector.

      • The AvailabilityCheckerImpl is more targeted towards content-apps and has at least some JCR-specifics, which do not make sense in the pulse-context.
      • The DefaultContentConnector is really a null-implementation and not a default one.
        It would make sense to resurrect the DefaultAvailabilityChecker and use that one. ContentConnector is not really needed I guess?

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                sang.ngo Sang Ngo Huu
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD