[MGNLUI-6795] Move valueContext setting in ContentDetailSubApp so it is ready at form creation Created: 19/Jul/21 Updated: 16/Feb/22 Resolved: 11/Feb/22 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2.10 |
| Fix Version/s: | 6.2.17 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jonathan Ayala | Assignee: | Fernando Cherchi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 0.25d | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Release notes required: |
Yes
|
||||
| Date of First Response: | |||||
| Sprint: | Nucleus 3 | ||||
| Story Points: | 2 | ||||
| Description |
|
Currently valueContext is set at the end of start method of ContentDetailSubApp, which makes not possible to access the current value when the form is created. Some users need to perform some actions related to the current item in their custom fields and this is not possible. By moving this operation, before the form creation, they would benefit from this useful feature. PR with the change has been created. |
| Comments |
| Comment by Fernando Cherchi [ 10/Feb/22 ] |
|
ValueContext is now provided earlier so it is available when form is created. |