(redux-form) Please restore redux-form onBlur workaround

[SpencerWhitehead7]

I have little hope for this request since its removal was explicitly called out in the 3.0 changelog, but I thought I might as well ask. My workplace and many other projects still use redux form, and switching off it would be a massive endeavor. Its NPM download rate has also stayed consistent, even after the release of final-form.

I love this library and we use it for all our phone number needs, but I'm worried the onBlur bug will make it unworkable. Would you be willing to reimplement the workaround, or to accept a PR that does?

original issue in 2017: #49
original fix: e3404f6

[catamphetamine]

Hi.
Going with 3.x meant a full spring cleaning of the code and I decided to remove anything that isn't required in terms of a modern setup.
redux-form surely will be used in tons of legacy projects, but I'm seeing the shift to things like Formik, react-form-hook, or stuff like that.
Even on the main page of redux-form the author states that new projects should not use redux-form because it's counter-productive performance-wise.

That being said, version 2.x isn't obsolete or anything: it just won't be getting any new features.
It can only get some small bug fixes if required.

[SpencerWhitehead7]

Well, fair enough. Maybe we'll stay on 2.x until we get it together to switch to final-form or react-hooks-form. Thank you for explaining the reasoning and answering so promptly.