[MGNLUI-3638] Resurrect the DefaultAvailabilityChecker and use that one in pulse-context Created: 29/Oct/15  Updated: 08/Mar/21  Resolved: 08/Mar/21

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 5.4.x

Type: Improvement Priority: Neutral
Reporter: Sang Ngo Huu Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLUI-3590 Make bulk actions configurable in the... 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)

 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?

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