search

redpanthers / starter

New rails project startup template to speed up project start time.
3 stars 3 forks source link

Add simple_form #9

Open tony-rp opened 6 years ago

coderhs commented 6 years ago

So we need to finalize the right approach to go here. If the new application in which people are going to use our template is going be the backend of react/angular/vue. Then having too many gems for the view would be a waste. So how do we account for such cases?

My idea for the initial version was to place all the protocols, gems, etc for the backend and then debate over the frontend later. Perhaps we could new branch for each frontend framework and have also included all the libraries that we commonly use for frontend frameworks also included there.

What do you guys think? @redtachyons @tony-rp

tachyons commented 6 years ago

It is fine to be opiniated about here. I prefer to go with simple form. And if we are using js frameworks, then it is just a matter of removing a gem from Gemfile

alan-redpanthers commented 6 years ago

I would prefer to have the master branch clean with just the absolutely necessary gems like simple form and haml/slim templating.

Front end frameworks could be implemented in respective branches, if necessary.

coderhs commented 6 years ago

then it is just a matter of removing a gem from Gemfile

Can't agree 100% to that because. 1) Simple Form will have configurations, that we will be adding extra, they too need to be removed. 2) It's not just simple_form there are going to be more gems like simple_form we will add for the view.