[MGNLUI-5666] Streamline ValueContext provisioning in choose dialogs Created: 13/Feb/20  Updated: 18/Feb/20  Resolved: 14/Feb/20

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

Type: Improvement Priority: Neutral
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed 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)
Sprint: UI Framework 16
Story Points: 5

 Description   

Choose dialog typically manage the value context on their own and => are supposed to bind it themselves. However, due to a wrong component provider used to construct the action bindings of the chooser the latter get an outer UI context's value context injected.

As a current workaround chooser interface exposes the getValueContext API, which can explicitly provide a value context to be used in actions, but that API is out of place, in-essential and needs to be removed, the context provisioning should be streamlined (be means of using the same component provider for both the view and the actions fired against that view).


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