Template path misbehaving

[pitr]

Template path misbehaving

[whitehat101]

If you have been fiddling with the ignore prefix, then that might explain this behavior. Rails will cache templates after it renders them. If the source file doesn't change, then the template won't get recompiled if you change the ignore_prefix until the source template gets modified.

Try setting:

# config/environments/development.rb (and production.rb if you deployed)
config.assets.version = "something new" 

Or nuking your tmp/ directory.

I set my assets.version to "#{Time.now}" when I was doing heavy development on this project. It invalidated all the cached assets every time I booted rails server.

[GriffinHeart]

@whitehat101 that indeed seems to fix it.

Any way to prevent this happening? Seems like an hack to use assets.version

[whitehat101]

I bet this is the same root cause as issue #37.

It's what asset.version if for, but having the user have to know about it is unexpected. It should probably be documented or...

sprockets-rails does this source:

# Configuration options that should invalidate
# the Sprockets cache when changed.
app.assets.version = [
  app.assets.version,
  config.assets.version,
  config.action_controller.relative_url_root,
  (config.action_controller.asset_host unless config.action_controller.asset_host.respond_to?(:call)),
  Sprockets::Rails::VERSION
].compact.join('-')

Since the length of the app.assets.version string doesn't seem to matter, I bet we could append ignore_prefix to config.assets.version so that the user never has to manually change the asset version because he or she changed a-r-t's config.

I don't know what the difference is between app and config .assets.version. I bet it's a Rails 3/4 thing.

We'd have to check the versions of sprockets and sprockets-rails that rails 3 and rails 4 pull.

[whitehat101]

Since I realized I could put templates in app/assets/templates (instead of app/assets/javascripts/templates) ignore_prefix became kinda useless to me. Neither the asset path nor the angular name contain templates, so they are both night and tight.

I'm a little concerned about collisions e.g.:

file	asset path	angular name
app/assets/templates/modal.html.haml	/assets/modal.js	modal.html
app/assets/javascripts/modal.js.coffee	/assets/modal.js

But since I keep my directives in javascripts/directives, collisions just won't happen. I know not to name a template the same name as a top-level js asset. For my angular projects, that typically only means I can't name a template app or application.

[pitr]

thanks @whitehat101 PR merged, v0.1.2 is out