Vaibhav Srivastava

@mathieujobin Yes, It is a problem with the gem. With latest sprockets extension chaining is no longer supported and extensions like `.jst.hamlc` are needed to be explicitly registered. I don't...

I have found a workaround as mentioned below i.e. by registering `text/hamlc` to `application/javascript+function` as Sprocket provides a JSTProcessor for `application/javascript+function => application/javascript` ``` ruby # lib/haml_coffee_assets/rails/engine.rb:38 env.register_mime_type 'text/hamlc', extensions:...

Shouldn't it be the `mtime` of asset itself as it was earlier? ``` ruby asset.mtime.iso8601 ```