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

Add precompiled template (js target) support to ruby haml #10

Open
mehcode opened this issue Apr 18, 2013 · 8 comments
Open

Add precompiled template (js target) support to ruby haml #10

mehcode opened this issue Apr 18, 2013 · 8 comments

Comments

@mehcode
Copy link
Contributor

mehcode commented Apr 18, 2013

https://github.com/elfsternberg/grunt-ruby-haml/blob/master/src/ruby-haml.coffee#L18-L19


This seems like something nice to have as the current ruby haml implementation only allows for an html target.

To be clear — I'm not going to be working on this; I'm just posting this as a possible enhancement that anyone is welcome to do.

@joneshf
Copy link
Contributor

joneshf commented Jun 20, 2013

Wait, what is supposed to happen here? Are we adding support for js to grunt-haml, or to grunt-ruby-haml?

@mehcode
Copy link
Contributor Author

mehcode commented Jun 20, 2013

grunt-ruby-haml (in my opinion) is a superfluous project that could be merged into this project. I had this idea before we had ruby support here. Now we have ruby support here but only for server-side templates. We don't have support for target: 'js'.

@joneshf
Copy link
Contributor

joneshf commented Jun 20, 2013

Gotcha, so add js support to grunt-haml.

@robwierzbowski
Copy link

Shouldn't this be added at the Haml level, and then bubble up into grunt-haml?

@mehcode
Copy link
Contributor Author

mehcode commented Jan 9, 2014

@robwierzbowski I wouldn't think that the project would care to provide JST when its meant (as far as I know) for server-side templating. But if someone can work it in there then that would be better, I agree.

@robwierzbowski
Copy link

Edit: Not sure how the grunt task can act anywhere besides on the server. I might not be understanding, but if the goal is to include JST files that are rendered by node in a Haml template, wouldn't you have a two part process: first use a grunt plugin designed for your particular flavor of JST to render JST to HTML, then include that HTML with grunt-haml/Haml?

@mehcode
Copy link
Contributor Author

mehcode commented Jan 9, 2014

Not sure how the grunt task can act anywhere besides on the server.

For our stack at @concordusapps we use grunt-haml to transform haml files to JST and rendered using chaplin on the client. Simple demo we showed off a while ago: https://github.com/concordusapps/chaplin-demo

@robwierzbowski
Copy link

Thanks, I'll take a look. Appreciate the grunt task, by the way.

Rob Wierzbowski
@robwierzbowski http://twitter.com/#!/robwierzbowski
http://github.com/robwierzbowski
http://robwierzbowski.com

On Thu, Jan 9, 2014 at 2:23 PM, Ryan Leckey [email protected]:

Not sure how the grunt task can act anywhere besides on the server.

For our stack at @concordusapps https://github.com/concordusapps we use
grunt-haml to transform haml files to JST and rendered using chaplin.
Simple demo we showed off a while ago:
https://github.com/concordusapps/chaplin-demo


Reply to this email directly or view it on GitHubhttps://github.com//issues/10#issuecomment-31966502
.

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

No branches or pull requests

3 participants