fix(Form)!: include nested state in submit data #3028
Draft
+23
β11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
#2889
β Type of change
π Description
Fixes an issue with nested form state not being included in the
@submit
event payload.The proposed solution requires to apply schema transformation to the state (partially reverting #2701) to return the
props.state
object in the submit event data.Another alternative would be to return a list of objects in the submit payload (with transformation applied) instead of the full object. We can't easily reconstruct the full object since we don't have the information of a nested form's state path within the parent form's state.
I added a new
transform
options in the form's validate function to control when transformations are applied. It's currently done on submit only.π Checklist