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.
97e236aReplaced usages of for...of construct for stupid IE (#2724)
892f45bFix #2718 (Incorrect way of accessing syncErrors, syncWarnings in ConnectedField, ConnectedFieldArray, ConnectedFields for redux-form/immutable) (#2721)
27211eeAdded meta.form to FieldArray props (#2712)
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
redux-form just published its new version 6.6.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
Bug Fixes
propTypesforwarnandvalidate. 08a377esyncErrorswhen usingredux-form/immutable. #2755propTypesfor diehardforbidExtraPropspeople. #2738 #2707 #2744STOP_SUBMIT. #2731 #2591Features
dispatchandpropsparameters to form-wideonChange. #2748 #2728The new version differs by 783 commits .
2a86b09v6.6.17c0ae04styling fixes on react-widgets example162cf46Fix #2591: stopSubmit removes pending promise from reduxForm. (#2731)c427875Fix triggerSubmit/clearSubmit propTypes problems (#2738)494f023Change the form-level onChange to accept the same args as onSubmit (#2748)17af992Fix: hasError used plain.getIn(syncErrors, key) for Immutable instead of getIn(syncErrors, key) (#2755)3292f65Fix 'renderHobbies' was used before it was defined eslint error (#2750)09a24adUpdated deps for examples08a377efixed warn and validate propTypescb655a4v6.6.097e236aReplaced usages of for...of construct for stupid IE (#2724)892f45bFix #2718 (Incorrect way of accessing syncErrors, syncWarnings in ConnectedField, ConnectedFieldArray, ConnectedFields for redux-form/immutable) (#2721)27211eeAdded meta.form to FieldArray props (#2712)a5fc53bUpdate propTypes.js (#2707)bd4d1fbAdd missing prop types for Field, FieldArray and Fields components (#2709)There are 250 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.