You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 14, 2022. It is now read-only.
First of all, congrats. I find this library very good and especially on a very good path.
My go-to currently is mobx-react-form. As you surely know, it has some issues when dealing with complex forms. Not all functions work as intended and so on
My question is: What made you think it was better to make a different library rather than forking and fixing mobx-react-form? Architecture? Too many bad / leaky abstractions? It is of special interest to me because I was just trying to do that.
I am interested in finally getting a good form solution. Like come on it's just a form right? I can help you with this project.
The text was updated successfully, but these errors were encountered:
Thanks. I think my implementation is better because you can use any validation lib or also create your own logic for it. You can choose not to use validation if you don't need to. By default react-fluid-form uses yup. In my opinion, yup is perfect, it's possible reuse logic from other solutions (react or not), like formik, that use this lib.
Mobx-react-form uses classes to create forms, it is not prepared to use react hooks. I preferred to create this library from scratch rather than forking mobx-react-form because I wanted to develop a small and lightweight code, using a modern way of writing react code. Also, I use some methods to make the form more performant with mobx. The architecture of the two libs is different.
Yes, it would be great if you want to contribute to this project. I really appreciate it! Thanks!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First of all, congrats. I find this library very good and especially on a very good path.
My go-to currently is mobx-react-form. As you surely know, it has some issues when dealing with complex forms. Not all functions work as intended and so on
My question is: What made you think it was better to make a different library rather than forking and fixing mobx-react-form? Architecture? Too many bad / leaky abstractions? It is of special interest to me because I was just trying to do that.
I am interested in finally getting a good form solution. Like come on it's just a form right? I can help you with this project.
The text was updated successfully, but these errors were encountered: