[MGNLUI-5335] DOC: Form property value access (API) Created: 20/Aug/19 Updated: 02/Sep/19 Resolved: 27/Aug/19 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | 6.2 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Ashraf Khamis | Assignee: | Ashraf Khamis |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | Datasource, new-UI-framework, new-data-binding, new-form | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Epic Link: | DOC: Documentation for Magnolia 6.2 | ||||||||
| Sprint: | UI Framework 5 | ||||||||
| Story Points: | 0.5 | ||||||||
| Description |
|
As forms now only write the changes to an item when some sort of 'commit' action is triggered, any pending changes are effectively stored in the form's binder/field components. What is needed is an API that would make it possible to access the property value by property name (optional) and by locale (optional). For more information, see |
| Comments |
| Comment by Ashraf Khamis [ 27/Aug/19 ] |
|
Final code changes too minor to document: Possible candidate for release notes. Discussed with Sasha. |