Actor Validation
Features
Cross-Actor Validation
Default Value
General
A
save
orsubmit
action in an actor can trigger front-end validation in multiple actors before the data is posted to the backend.{ "name": "actionName", "actionType": "submit", "validation": [ "actor1", "actor2", ... ], ... }
- A
normal
action won't trigger front-end validation by default. But it can be configured to do the front-end validation before its handler is triggered.
Status
Release Available | Status | Framework Name |
---|---|---|
2.9 | Current | TBC |
Actor Validation Enhancement
Default Value
General
- For save and submit actions, they validate their own actor (the actor that contains those actions) by default before the remote API is called. If there are any field validation errors in the actor, the first invalid field will be scrolled to be visible.
- For any action object, the validation key can be added, which takes an array of the actor names so that when the action is triggered, the data in those actors will be validated. If there are any field validation errors in the listed actors, the first invalid field in the first listed actor will be scrolled to be visible.
Status
Release Available | Status | Framework Name |
---|---|---|
3.5 | Current | TBC |