Ability to get .html file under assets without converting to a template?

[pitr]

Ability to get .html file under assets without converting to a template?

[elado]

Hmm, after patching the gem it seemed to break things with external libraries. I also found out that it supports the extension .ajs.

I use angular-ui-bootstrap and I load some templates with:

//= require angular-ui-bootstrap/template/tabs/tabset.html

My patch (commenting the .html engine registration) broke it.

Maybe a better way is to whitelist/blacklist files/folders?

[dmathieu]

Why would you want to do that?

[pitr]

anything under app/assets/javascripts should be converted to JS at the end. I'd put your html files in public folder, or app/assets/html or something

[elado]

1. I work with component folders rather than split filed by type

So I have /app/assets/app folder which contains sub folders with all js/css/html. For example, a directive of a follow button:

app/assets/app/components/follow/directive.js.coffee
app/assets/app/components/follow/style.css.scss
app/assets/app/components/follow/button.html

I don't find any logic in having all files split into 3 different folders (try it--it's much more convenient!).

2. I use bower to include 3rd party libraries. That means I have /vendor/bower_components/ folder with full libraries like angular-ui-bootstrap that contain all JS/CSS/HTML scattered under it.

I wanted to be able to choose when to convert an HTML file to a template and when not to, since I still want some .html templates in the asset pipeline to be lazy loaded by angular. I realized that I can do that by giving a different extension, e.g. button.tpl.

[pitr]

I'm glad you came up with a solution.

Splitting by component is a nice idea. Did you have any problems with Rails? AFAIK it expects app/assets/{TYPE} folders.

[elado]

In my application.rb I have:

config.assets.paths << config.root.join("app", "assets", "components")
config.assets.paths << config.root.join("vendor", "assets", "bower_components")

Rails asset pipeline doesn't really care about the content of the file or its location, as long as it's under assets.path. That way I don't need to put js under javascripts, css under stylesheets and html under public, they're all in the same folder, app/components.