Form level validation state mutation

[Hyperkid123]

part of #687

Changes

• add state mutation after form level validation
• synchronizes form-level and field-level validation errors and state flags

[codecov]

Codecov Report

Merging #719 into state-manager will increase coverage by 0.07%.
The diff coverage is 100.00%.

@@                Coverage Diff                @@
##           state-manager     #719      +/-   ##
=================================================
+ Coverage          93.06%   93.13%   +0.07%     
=================================================
  Files                220      220              
  Lines               3574     3613      +39     
  Branches            1133     1138       +5     
=================================================
+ Hits                3326     3365      +39     
  Misses               248      248              

Impacted Files	Coverage Δ
...ckages/form-state-manager/src/utils/manager-api.ts	96.52% <100.00%> (+0.71%)	⬆️
...s/form-state-manager/src/utils/use-subscription.ts	97.77% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee43d6c...14627f9. Read the comment docs.

[rvsia]

Can we avoid this? This is not how the form currently behaves (check it here) and it brings performance issues (why to validate fields that have been already validated?)

Also, it means that active field is being validated 2x: field validation > form validation > field validation

[Hyperkid123]

It definitely can and should be. I wanted to postpone this after we have the memorize functionality implemented because that is a big part of it.

The validation will have have to run twice at some point (it does in the example as well) because the validation functions are different.

Once we have the memo we can "save" the active field revalidation by running the field level after the form level and check if it was validated in that cycle.

[Hyperkid123]

🎉 This PR is included in version 3.1.0 🎉

The release is available on

• react-form-renderer (@latest dist-tag)

Demo can be found here!