[MGNLUI-6310] Address problems in chained actions Created: 12/Oct/20  Updated: 06/Nov/20

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

Type: Improvement Priority: Neutral
Reporter: Šimon Demočko Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: needs-discussion, ui-ux-impr
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)

 Description   

ChainedActions spec shouldn't let certain steps to be deliberately skipped just because of availability. Either all steps should be done or none (fail).

Or deprecate ChainedAction

  • and supersede with MGNLUI-5949
  • use custom actions wherever ChainedAction was used internally

Someone can already be using it in a way that it skips instead of breaks (we could introduce breakage in minor)

 

Will need more discussions

consider if we want to have actions composable, or rather consider them atomic and use custom actions for anything more complex


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