Update redux-form to version 6.0.1 🚀 #86
Open
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.0.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
🎉 🎉 IT'S HERE!!! 🎉 🎉
Thank you SO MUCH to all of you who have helped test and improve
v6over the past four months.(It's called
v6.0.1because of a previous mistake with npm...oops.)v5→v6Migration GuideChanges since
v6.0.0-rc.5Bug Fixes
dispatchto props forField. #1569 #1567blurandchangeactions in form props. #1588 #1579Fieldscomponent. #1589 #1583FieldArraywas rerendering on every value change. #1590 #1578undefinedinto an array. #1591 #1574FieldArraywould not rerender on add/remove. #1594 #1592initialValuesprop to form component. #1598 #1570_errorwasn't flippingvalidandinvalidflags. #1606 #1603Features
v5. #1620 #1614Breaking Changes
defaultValueprop toField, at was causing confusion. If you have a field that requires a type other than string, you should provide the value viainitialValues. #1593 #1341The new version differs by 514 commits .
d664dc3changed version to 6.0.17f03469v6.0.0 release!3fac81bFixed broken RadioButtonGroup Material UI implementation. #15994bcded6Implemented autofill feature from v5 (#1620)312e250v5.3.3238bea7Merge branch 'v5'2133ec7Form-wide _error wasn't flipping valid flag (#1606)8e200076rc5 docs link3fd2dfcPassthrough the initialValues prop to the enhanced component. (#1598)d2c8f29Fixed bug where FieldArray would not rerender on add/remove (#1594)d46b183Updated all deps! 🎉a52af30Consolidated webpack configs58fcf25Clarified that FieldArray prop functions are not mutators. #1544e34acb9fixed doc error pointed out in #1515fa8bc56updated examples to react 15.3.1There 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