Update redux-form to version 6.3.1 π #66
Closed
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.
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 β¨
You rock!
π΄
GitHub Release
FormSection
in 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 aFieldArray
render function. #2247 #2215The new version differs by 667 commits .
d34751f
6.3.1
2e7d4ab
6.3.1
c4dfa70
Merge remote-tracking branch 'origin/master'
1016da6
fixed warnings during Fields test
c62adfc
Implemented fields.get() (#2247)
65b550e
fixed a duplicate periods (#2226)
25fb646
* Persist errors through initialize action (#2228)
c22ab5f
add clearAsyncError feature (#2213)
8ffd57f
Only wrap
FormSection
indiv
if necessary (#2218)e5f8557
Resolved conflicts
89924e0
Resolved conflicts
d84aa7f
Allowed submitting when submit errors exist (#2246)
83af3f2
6.3.0
e6a3cc8
6.3.0
7179229
Field-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? β‘
greenkeeper upgrade