Lazy evaluation of form and field state

[erikras]

Has the added benefit of making all the state values readonly.

That should only be a breaking change for the naughtiest of users.

[codecov]

Codecov Report

Merging #596 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #596   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          16     17    +1     
  Lines         234    248   +14     
  Branches       57     57           
=====================================
+ Hits          234    248   +14

Impacted Files	Coverage Δ
src/FormSpy.js	100% <ø> (ø)	⬆️
src/Field.js	100% <ø> (ø)	⬆️
src/getters.js	100% <100%> (ø)
src/useField.js	100% <100%> (ø)	⬆️
src/useFormState.js	100% <100%> (ø)	⬆️
src/renderComponent.js	100% <100%> (ø)	⬆️
src/ReactFinalForm.js	100% <100%> (ø)	⬆️

---

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 60434b8...7d12161. Read the comment docs.

[Andarist]

@erikras are u sure this is safe? seems really unsafe to async react

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

[erikras]

Can you explain why? I'm not sure I understand. How is accessing a getter less "sync" than a property? This also makes them readonly.

[erikras]

Published in v6.3.1.