Closed normally-andrew closed 12 years ago
I think that someone else just asked for Jammit to never package assets in test ... which is why it behaves the way it does.
Can't you just force the packaging back on manually in your test environment?
Indeed, someone did. I'd love to force packaging back on in test, but I don't know if there is a way to do that.
The assets.yml
file supports ERB, so you can simply interpolate the value you like, in the environment you like.
So you mean doing something like this:
<%= "package_assets: true" if ENV['RAILS_ENV'] == 'true' %>
will override the default for the test environment?
Yes, I do.
<%= "package_assets: true" unless Rails.env.development? %>
Thanks, ended up just setting package_assets to 'always', got the job done.
We're using Jammit to package several JS templates into one namespace. When we run our Capybara integration tests, the namespace doesn't exist because Jammit isn't packaging, and the tests error out.
I realize the logic for not packaging assets in test, but is there a config to turn it back on?