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.
This has been a source of conflict for users of this library since its release. To some people, it makes sense to write a validation function to validate the entire form, and for others, it makes more sense to write individual validation functions for each field. Those of you favoring the latter are in luck! You can now do things like:
constrequired=value=> value == null?'Required': undefinedconstminPasswordLength=value=> value && value.length <3?'Must be longer': undefined
<Fieldname="username"component="input"type="text"validate={required}/> // <------------
<Fieldname="password"component="input"type="password"validate={[ required, minPasswordLength ]}/> // <------------
Hello lovely humans,
redux-form just published its new version 6.3.0.
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
This has been a source of conflict for users of this library since its release. To some people, it makes sense to write a validation function to validate the entire form, and for others, it makes more sense to write individual validation functions for each field. Those of you favoring the latter are in luck! You can now do things like:
Bug Fixes
"1."
and1
as equal. #2209The new version differs by 654 commits .
83af3f2
6.3.0
e6a3cc8
6.3.0
7179229
Field-level Validation (#2245)
c679dd2
Change setIn to work with seamless-immutable. Fixes #2204. (#2219)
37adcbe
deepEqual fix so it doesn't treat 1 and 1. as equal (#2209)
ef66e99
updated example deps
6083719
updated example deps
4855bc0
updated version numbers
a442480
6.2.1
1250fd8
Pass reference to the
fields
prop (#2187)439904c
Merge pull request #2171 from martinhorsky/master
beb52ff
Merge pull request #2175 from huan086/setInPerformance
1cf3829
Rewrite setInPath for 2.5x speed improvement.
a29c29e
Allow null to empty string conversion override using format
4326509
Merge pull request #2170 from oyeanuj/patch-1
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