Skip to content
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

Choosing haml as a template engine #233

Open
thenickcox opened this issue Aug 25, 2015 · 1 comment
Open

Choosing haml as a template engine #233

thenickcox opened this issue Aug 25, 2015 · 1 comment

Comments

@thenickcox
Copy link

This is a port from this issue I filed on rails-stripe-membership-saas. The full text follows:

Firstly, thanks a ton for this project!

This is a weird bug, and I'm not totally sure how it happened. Choosing haml as a templating engine works entirely, except that app/views/devise/registrations has the following files in it after app generation:

edit.html.haml
new.html.erb
new.html.haml

So rails renders new.html.erb preferentially. I was suuuper confused, because new.html.erb doesn't contain anything about checkout. So in essence it looks like the app doesn't contain a checkout, which is the point. This works if you just delete new.html.erb. But it took me a good while to figure that out. (Probably too long, admittedly.) I was able to duplicate this with another generation in another directory.

Edit

Happy to submit a patch if you point me to the right place.

@thenickcox
Copy link
Author

It looks possible that devise getting copied over happens after the conversion from erb to haml:

destination_filename = destination_filename.gsub(/.erb/, '.haml')

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant