[MGNLUI-5189] Ability to configure own success/error message (DefaultAsyncActionExecutor) Created: 13/May/19 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Laura Delnevo | 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)
|
| Date of First Response: | |
| Epic Link: | UI framework implementation |
| Description |
|
Improvement request The Add-On team would like the ability to configure our own success/error message; without relying on the current temporary solution via DefaultAsyncActionExecutor (CommandActionTriggerListener). This might require the Core team to re-designing the action/command. Related ticket Please note that the LC project is not blocked by this requirement, but it would be a good improvement to incorporate. // efochr ilgun will be able to provide more details on this request if/when needed |
| Comments |
| Comment by Roman Kovařík [ 10/Mar/21 ] |
|
Closing this as AsyncActionExecutor was deprecated. |