The field hierarchy is now kept in the form binders, so technically it is available while form is active and could be injectable in the validators and/or fields themselves. Need to see how to better expose such hierarchy and how to address at least some of the issues related to the topic.
User benefit:
- See only relevant values in form fields. Make fewer mistakes and fill the form faster.
- Populate and validate the options in one field based on what the user chooses in another field.
Timebox to 13 SP, possible followed by smaller efforts.
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | DEV-920 |
---|
|
Enables:
Jira |
---|
server | Magnolia - Issue tracker |
---|
serverId | 500b06a6-e204-3125-b989-2d75b973d05f |
---|
key | MGNLUI-2542 |
---|
|