This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of redux-form.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Hello lovely humans,
redux-form just published its new version 6.3.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of redux-form. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
FormSectionin a<div>if absolutely necessary. #2218this.props.clearAsyncError()function to allow clearing an async error for a specific field. #2213 #2214fields.get()andfields.getAll()to provide access to array values when inside aFieldArrayrender function. #2247 #2215The new version differs by 667 commits .
d34751f6.3.12e7d4ab6.3.1c4dfa70Merge remote-tracking branch 'origin/master'1016da6fixed warnings during Fields testc62adfcImplemented fields.get() (#2247)65b550efixed a duplicate periods (#2226)25fb646* Persist errors through initialize action (#2228)c22ab5fadd clearAsyncError feature (#2213)8ffd57fOnly wrapFormSectionindivif necessary (#2218)e5f8557Resolved conflicts89924e0Resolved conflictsd84aa7fAllowed submitting when submit errors exist (#2246)83af3f26.3.0e6a3cc86.3.07179229Field-level Validation (#2245)There are 250 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade