Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basically no activity in the last 4 months =( #4426

Closed
kylebebak opened this issue Apr 6, 2019 · 15 comments
Closed

Basically no activity in the last 4 months =( #4426

kylebebak opened this issue Apr 6, 2019 · 15 comments
Assignees

Comments

@kylebebak
Copy link

kylebebak commented Apr 6, 2019

1 commit in the last 4 months for a library with almost 2000 commits in the previous 3 and a half years... A betting man would have to bet that redux-form is stuck, and that basically none of the open issues will be addressed, much less fixed.

I think I can speak for thousands of people when I say it'd be nice to have some visibility into plans for this project. Do the maintainers plan to continue development?

@gustavohenke
Copy link
Collaborator

Uh, there were quite a few commits in the last 4 months...

Screen Shot 2019-04-08 at 11 33 19

yay, including christmas commits! 🎄

But yeah. The library is quite dead yes. Erik's focus is definitely on Final Form these days.

I have been a contributor since 2016 and I never really got to do code changes.
Redux Form is just too complex, and nearly everyone who wants to take a stab gets/will get frustrated by the codebase.

There was a trend some time ago that everything should be kept in the Redux store, but nowadays this trend seems to be dying (well, not that I have done much work with Redux since then) -- and form status definitely shouldn't.

I'll leave it to @erikras to add more insights.

@qjnz
Copy link

qjnz commented Apr 8, 2019

It is easy to migrate to Final Form, probably it is what we should be focusing on.

@kylebebak
Copy link
Author

kylebebak commented Apr 8, 2019

@gustavohenke

Thanks for the info Gustavo! You're right about there being more commits in the last 4 months -- I meant to say one new commit in 2019 =P

I don't mind being downvoted if it means there's more info about rxf's future. Dead is a strong word, and that's a very compelling reason not to use rxf for a new project, which is useful info for anyone that sees this issue.

I think it's a shame, because rxf is a great library with a comprehensive API. It takes a while to get the hang of it, but it's very powerful. It would be great to see continued improvements, and IMO would continue to make rxf a great option for managing form state, even if the pace of development really slows down.

It looks like React Final Form hasn't quite caught on the way rxf did. Should people try Formik? It seems like it borrows heavily from rxf, but has a more active community and gets more love from its maintainers, at least as of April 2019.

Or should they try RFF? I'd love to hear from @erikras that the same thing that happened to rxf isn't going to happen to RFF...

@QJLEE
Do you know of any migration guides from rxf to RFF?

@tyscorp
Copy link
Contributor

tyscorp commented Apr 9, 2019

It is easy to migrate to Final Form, probably it is what we should be focusing on.

Not if you use immutable, which Final Form doesn't support. :(

@sanchan
Copy link

sanchan commented Apr 25, 2019

I've just started a new project and I was in the process of integrating redux-form and reading your ticket @kylebebak I heard about React Final Form, I guess is time to move and say goodbye to redux-form for future projects, so upvote for you to compensate the downvotes.

@Asday
Copy link

Asday commented May 22, 2019

It is easy to migrate to Final Form, probably it is what we should be focusing on.

Unless you actually want to keep your form state in the store, which is an entirely reasonable thing to want.

Seems we need some sort of outreach to recruit some maintainers for this project that can handle it, as it's clearly still wanted:

image

As you're experienced in the matter, @gustavohenke - do you have any ideas?

@erikras
Copy link
Member

erikras commented May 23, 2019

Maintainers Wanted

Hi, guys. I'm the original author, and I no longer use Redux-Form in my own projects, because I've written a similar solution that I consider to be better in almost every way, React Final Form. I recently added a note to this effect to the readme. I would love for Redux Form to live on, but I just don't have the time or desire to shepherd it into the future. #4431 is a rather large boulder on the path to the future, which I put quite a bit of effort into, but I can't spare any more.

If anyone would like to step up to lead Redux Form into the future, I'd be happy to hand over the reins.

@Asday
Copy link

Asday commented May 23, 2019

I sure would love to see the call for maintainers in the readme, too, Erik. :)

@kylebebak
Copy link
Author

Thanks for the update @erikras , and I think I'll be trying React Final Form in my next project.

For those that are interested in migration guides, I've heard this video is helpful.

@erikras
Copy link
Member

erikras commented May 23, 2019

@kylebebak I was all like, "Ooh! Someone made a migration video!" 🤣🤣🤣 Yes, that's the most useful video I've made.

@Asday Not a bad idea.

@renatoagds
Copy link
Contributor

@erikras I would like to join as maintainer. I worked for the last few years with ReduxForm and helped the project in a few opportunities.

@zazapeta
Copy link
Contributor

Hi there,

As a lover of redux-form (I learn so much with you @erikras - selectors, actions, ducks, renderProps, decoupling app, documentation, create a nice public api... - thx for that !!) - I really want to help to maintain the repo, but I'm a little bit a noob, sorry.

Even so, can I suggest a re-write of redux-form by using React-Final-Form (that seems to be the right way) behind the scene ? Including a tiny 'conf/adaptater' file to tell to React-Final-Form what to sync in the redux store and what to let in the local state.
Moreover, the base code is huge (and awesome !). I want to help on it, but my little brain is not ready. (someday...) . I think I am not alone in this case, and this is why I suggest a re-write.

If so, I wonder if can i take a part of this 're-write'.

What do you think ?

Thx for reading,

Cheers 🍻 - zazapeta

@Asday
Copy link

Asday commented May 25, 2019

If that's a possibility, then perhaps its a good idea going forwards, but I'm not going to go back and rewrite my old projects to use an entirely different form framework, and my employer sure as heck won't pay me to do the same, either.

There's nothing actually wrong with redux-form, save a couple little bugs, and being a little behind react-redux. All it needs is a couple maintainers like @renatoagds, who's already doing good work on the bugs.

@renatoagds
Copy link
Contributor

renatoagds commented May 26, 2019

Hi all, I step up as maintainer and I expect to change the scenario presented in this issue, based in that, we'll start:

  • A weekly patch/minor release, probably on Wednesdays.
  • Roadmap for v9. I opened an issue, to get ideas and feedback for the next major release. I ask help for everyone that's in this thread, to get involved in the plan for next version -> Roadmap - v9 #4467

Based on that, I'll close this issue since we have plans to return our activity.

@iamandrewluca
Copy link
Member

iamandrewluca commented Jul 26, 2019

@erikras I want to step in! We are using redux-form in production. And increasing number of issues and unmerged PR's makes me sad. react-final-form is not a solution for us.

The primary reason not to would be if your forms are very tightly coupled to Redux in some way, like if you need to manipulate form data by dispatching an action from outside the form component.
https://twitter.com/erikras/status/1035082880341483520

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants