[MGNLUI-748] Create a base implementation for ActionExecutor Created: 28/Feb/13  Updated: 25/Jun/13  Resolved: 25/Jun/13

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

Type: Improvement Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: actions, app-api
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
is causing MGNLUI-977 AbstractActionExecutor should be in t... 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)
Date of First Response:

 Description   

As we need to create actionbars not only in subapps, i.e. an optional actionbar in Pulse to act on workflow items, it would be convenient to have an abstract ActionExecutor implementation taking care of creating and executing actions, whilst leaving to subclasses how to retrieve an action definition.



 Comments   
Comment by Daniel Lipp [ 01/Mar/13 ]

New type deserves a unit test.

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