Skip to content
This repository was archived by the owner on Aug 23, 2022. It is now read-only.

React Redux Form v1.7.0

Compare
Choose a tag to compare
@davidkpiano davidkpiano released this 21 Feb 04:37
· 398 commits to master since this release

Performance Improvements + Optimizations (bf53863)

  • actions.promise will now treat rejected promise errors as async errors
  • model actions are now considered "external" by default - only when they are called within a Control event handler are they considered internal.
  • no validation will occur on Control components if there are no validators={...} or errors={...} props.
  • no validation will occur on Form components if there are no validators={...} or errors={...} props unless the form is made invalid (due to async validity) - then the validity will become valid again on next validation.
  • all validation originating from Form components are merged by default with field-level validation, instead of overwriting it.
  • (internal) isValid() correctly handles async simple validation (strings, boolean, etc.)
  • no ‘validate’ intent will be pushed if actions.change is not external (originated from Control). This saves a render!

Documentation Updates

  • Quick Start guide updated to clarify when you still need to use redux-thunk (which, for most use cases, you don't need to). #655
  • Quick Start guide also updated to clarify when you would use dispatch in handleSubmit(). #674
  • Lots of other small documentation updates: #673, #675, #676

Fixes and Enhancements

  • 🆕 The <Control persist={true}> prop now persists validity, even when the control is unmounted. This can be useful when you have multi-part forms and you need to go back to a previously rendered form, but want to remind the user what the errors currently are. #594
  • Using <Control mapProps={{...}}> on a plain <Control> will now behave with the same extend-like behavior in <Control.text>, <Control.radio>, etc. #653
  • 🚧 A stop-gap temporary <Form onBeforeSubmit={(event) => {...}}> prop will let you handle the event directly on every form submit. This will be fixed more holistically in version 2.0. #637