Weird templateCache issue. about angular-rails-templates HOT 4 CLOSED

Are you getting HTTP GET requests (in the console)? If you have a catch-all route in rails, and angular doesn't find the template in the cache it will make a GET to that URL. The catch-all would explain how the wrapping layout got into the cache.

Try setting:

# config/environments/development.rb
config.assets.version = "something new" 

If you already had templates in your assets dir, sprockets probably cached them and isn't recompiling because it believes the source template has not changed (and is just serving html, instead of the js that injects the templates into the cache)

I've been thinking about tying ART's version into the config.assets.version to help deal with sprockets caching quirks, but I haven't gotten to it yet.

from angular-rails-templates.

Ah! Ok so the layout getting wrapped was definitely as a result of my rails route catch all.

And the reason why angular was not finding my partials in the templateCache (causing it to issue a get to rails and thus getting the layout), is because I have a foo.js and directives/modal.js in my /assets/javascripts. This collides with the js files being generated by angular-rails-templates. So the question is, what's the best solution here? Can I get the generated js files to be at /assets/templates instead of /assets?

from angular-rails-templates.

Ah my templates are under /assets/templates and not /assets/javascripts/templates which is why I'm running in to this and not you/others.

from angular-rails-templates.

Maybe add something to the readme that indicates it makes .js files for the templates and that these can then collide with existing js files.

Closing as this turns into normal asset pipeline behavior.

from angular-rails-templates.