Alex Riedler
Alex Riedler
It looks like any two files on the asset path must have unique file names (upto path of the asset paths - excluding file extensions). It will grab whichever is...
I remember something weird about extensions and mime type relations...; something with rails during bootup changing something so that it does not work in initializers only in initialization:after of the...
The first works because the handlebars in slim needs to be treated like text; how slimbars is compiled is basically: Pass through slim compiler; than through the handlebars precompiler. slim...
In an ideal world; I would want to make slim/haml aware of handlebars blocks: e.g. {{#if foo}} h1 {{else}} h2 {{/fi}} p | yes this would work however that is...
https://github.com/jamesotron/hamlbars is sorta what you want but for slim, correct?
If you can think of a nice way to integrate (even just syntactically) slim with JS templating engines I would be really interested; I haven't invested much time into thinking...
I changed how registration is done in the **fix-sprockets-register** experimental branch (which is part of the next version). In order to get it to work for templates of the name...
@timherby, haha yeah, thanks for notifying me! and no problem!
@rpocklin I assume this is because the separation of pipelines that you are using. (or files are in both folders/symlinked) ? the 'handlebars_assets' gem does take '.hamlbars' files and compile...
At the same time it would be worthwhile to add an options string; for instance I want to compile with source-maps for development.