-
Notifications
You must be signed in to change notification settings - Fork 630
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
Formtastic 4.0 #1197
Comments
Just have to say keep up the good work guys, this is great! |
@javierjulio thanks for checking. Marked it as done. It was just me pushing through and I could not find the time lately. What would help is someone trying the git branch and checking if there are any issues with the upgrade. Then we could mark the beta release I guess. |
@mikz I'm asking since myself and a few others are new maintainers of ActiveAdmin. Formtastic gem is pretty important to us so we'd like to see it continue or look for a new solution. It seems the work is here it just needs some attention and a release. One of the last PR's you took was from @Fivell who is also an ActiveAdmin maintainer. I set Formtastic to master branch on AA locally, ran our test suite and everything is green. 👍🏻 I will do more testing with our sample app which has various form setups and that should really test Formtastic v4. How else can we help to get a release out? While its possible to modify the wrapping HTML of inputs, the fieldset/list wrapper is a problem. Would you also consider a change to make it easier to override the fieldset and list wrapper HTML output? Right now its in a module but done in a long method without a way of doing it. It would be helpful to have a way of modifying the HTML for all in v4 even if it means subclassing all inputs. |
@javierjulio I see there was a 1.0 release of ActiveAdmin, finally. I'd like to try to do normal beta releases of formtastic that would match releases of AA, so we don't have to target git, but just prerelease gem version. I wanted to make it a bit bigger release and pack more stuff into it, but that sounds harder and harder, so we might just release what is there now. I agree that customising the structure of generated forms should have a better story. I'm happy to see some examples on how that should work. Kind of unrelated PR, but similar approach was #1211. Having examples on how to use it and some prototype implementation would be nice so we can see how that would be used by people and affect the core. I'd definitely want to go through opened PRs and see what makes sense to try to get merged. Maybe not in the first beta release, but at least try to get it in later. There is a milestone https://github.com/justinfrench/formtastic/milestone/27 with issues I hoped we could get into beta release. We can do first beta with what is there now and then second one later. Right now only @justinfrench can do a release (#1200). So I think this might be good time to try to share those permissions, so I can do beta releases more often. |
@mikz @justinfrench How is 4.0 going? My PR #1272 got merged about 6 months ago, and I'm still pointing a project at my fork. I'd love to get it pointing to 3.2 or 4.0 instead. |
@dkniffin I understand that, but it is not going at all. I'm not actively using this project, so it is hard for me to work on it without any testing ground. We could try to release beta1 at least. WDYT @justinfrench? That would remove the git dependency and at least move us forward a bit, even when it would not be feature complete. |
Hey folks, sorry for the lack of inactivity. @deivid-rodriguez has been helping get master ready for a 4.0. I've released a 4.0.0.rc1 gem today, and I'm actively looking for new maintainers. |
New release of Formtastic is coming. #1108 (comment)
Major changes will be:
TODO
4.0-dev
to masterThe text was updated successfully, but these errors were encountered: