-
Notifications
You must be signed in to change notification settings - Fork 125
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
2.0.0 #77
Comments
Your suggestions make sense to me and I would appreciate it to seeing a 2.0.0 release in the future. |
Your suggestions are interesting, but looking through my Formsy components, they are all pretty beefy and unique. You're saying the old functionality would still work, right? This seems specifically for very simple inputs. |
As far as 2.0.0, I'm down to go in that direction. #48 is a great change. #50 needs documentation and testing. But that could be done more easily if it were part of a 2.0 development push. How does this sound for a plan:
How does that sound? |
I wouldn't do it on master. If we find a bug that could be fixed in 1.x it would become impossible if master is bumped to 2.0. How about a 2.0 branch which we can merge into master once it's good enough for release? |
True. The only downside to a branch is that last time I wasn't able to get it to download as part of a package.json for testing. I'm sure somebody here could help with that though. |
Inactive. Closing. |
Hi, fellow contributors. I feel the time has come to start considering a new major version release so that we can introduce some breaking changes and deal with issues that burden formsy from the old times when things were handled with mixins. Let's post ideas for 2.0.0 here as an "umbrella issue" so that we can start working on them and hopefully release a beta at some point. Also feel free to tell me that I'm dumb and we don't need a new major version ;)
For the starters, we have #48 and #50, both reviewed and awaiting merge, both with introducing breaking but much needed changes.
To start with ideas, one that I had is streamlining withFormsy. Currently, for each custom form element, we need to make a new component that renders the base one, an error message and copies the value to Formsy HOC's state. This is pretty simple but there's a lot of code, a lot of boilerplate to just copy-paste around. I'd like to improve this by making withFormsy work more like Redux's connect. Something like:
We could also make mapValue and renderWrapper from this example the defaults, so it would simply look like
and uses could still supply their own mapValue and renderWrapper for cases that differ from defaults. Should probably also allow onChange prop name override for base components that deviate from the standard.
This has multiple benefits over the current HOC:
Another idea would be performance issues. Aside from optimizing existing code if feasible, I'd also like to look into the possibility of marking elements as "isolated", meaning they don't affect rendering and validation of the form and other elements. With elements like these, we could opt to not rerender the form when they change. It would probably have to be calculated at runtime and not left to user to specify as a prop.
Any of this make sense to you guys or am I just rambling?
The text was updated successfully, but these errors were encountered: