Why does install generator include Devise and a User model? about railsui

[justalever]

Thanks for the feedback @petealbertson!

If you look at the README FAQ section, there's a section "What happens during installation?" that outlines the gist of everything.

We weave devise views into a typical template when installing one with Rails UI. Those views are customized based on Devise at this time but there is a future where I can see being able to choose to either opt out of generating a User model or have a different auth solution with pre-designed templates installed, we just aren't there quite yet.

Do you want to opt out of having the User model generated by default or prefer something other than Devise?

[petealbertson]

I missed the details in the README, but fwiw, your website docs do not have the same detail with regard to installation. All I saw was Additionally, it installs and configures a couple other handy gems Rails UI leverages inside most views.

Regardless, this is a UI tool so there is no logic to including models and migrations (let alone a very opinionated user auth gem) in the install generator. UI tools by definition should not include anything beyond front-end HTML/CSS/JS. Otherwise, you're not "RailsUI" but "Rails UI and User Auth". I would never choose a UI tool that makes those DB or model decisions on my behalf, so even an opt-in experience is questionable to me.

[justalever]

@petealbertson got it! Thanks for the feedback. The goal with auth-included is to solve the repeatable task of designing authentication views and mailers so you save time doing that yourself. I totally get it's not going to appeal to everyone.