Open sbusch opened 6 years ago
It mainly is a lack of time - it's in a stable state (I know a few companies using it in production) and I don't have time to handle the backlog of issues alone, many of which are probably invalid due to their extremely custom use-cases (it's virtually impossible to accommodate all use cases for forms in a single library).
However, I will continue to review PRs and welcome community contributions.
@davidkpiano, this is a great lib for those of us who have to store form state in redux. In my use-case I have several forms that need to keep their form values long after being unmounted. I don't think formik necessarily covers this use-case as of yet. Thanks for continuing to maintain it. This is the cleanest implementation of handling forms in redux that I've seen.
https://github.com/davidkpiano/react-redux-form/commit/c5d6d4d4a696dd5cc31da8c8721b3a6fd6af1dc3 annotates the GH front page with
We're quite happy users of React Redux Form and are wondering if it's just lack of time and/or maintainers or are there any technical reasons/design choices that can't be fixed?
@davidkpiano could you please elaborate on this?
I think Formik is quite nice, easy to use and leverages the current state-of-the-art approach of using render props. But it's still young and has it's own problems. Take a look at the unresolved issues and open PRs. For example I couldn't find a clear story how to create reusable forms parts with good encapsulation (which includes validation). Although I'm not an active user of Formik, I fear that it could be too limited, and I'm not sure if it can handle advanced or exotic use cases in the future.
OTOH
react-redux-form
is very flexible and I'm quite confident about it's future, because every part is composable and accessible (state, reducers, action creators, ...).Looking forward to your opinion, thanks!