[MGNLUI-5734] Let the basic dialog actions be available for empty value context by default Created: 15/Mar/20 Updated: 17/Mar/20 Resolved: 16/Mar/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2 |
| Type: | Bug | 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Release notes required: |
Yes
|
| Sprint: | UI Framework 19 |
| Description |
|
Unlike pre-6.2 dialogs, updated implementation applies availability check to the dialog actions by default. Apart from other implications, this also means the the dialogs actions have to be explicitly configured to be compatible with an empty values context case (aka root: true), which might not be convenient (and not expected by many). Proposed solution: let the default dialog actions (commit/cancel) have pre-configured availability definition with root property set to true. In case the user decides to have explicit availability configuration - they'd have to also configure the mentioned property explicitly. |