You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is an small application to show that sprockets-rails 3.1 is precompiling the assets when
the specs require them even having the configuration assets.compile = true.
This application raise an exception when the precompilation of the assets is executed. This is to
proof that assets precompilation is run when running tests that require them.
The test spec/views/welcome/index.html.erb_spec.rb just renders a view which calls <%= stylesheet_link_tag 'index' %> .
I may be seeing something related to this issue. I have tests failing during asset compilation following an upgrade of Rails 4.1.16 to Rails 4.2.7.1, which brings with it an upgrade of sprockets-rails from 2.3.3 to 3.1.1. My remedy thus far is to lock sprockets-rails at 2.x
You can visit this project
It is an small application to show that
sprockets-rails 3.1
is precompiling the assets whenthe specs require them even having the configuration
assets.compile = true
.This application raise an exception when the precompilation of the assets is executed. This is to
proof that assets precompilation is run when running tests that require them.
The test
spec/views/welcome/index.html.erb_spec.rb
just renders a view which calls<%= stylesheet_link_tag 'index' %>
.This test fails in
sprockets-rails 3.1
when trying to run the assets precompilation.You can checkout from the commit and run specs.
But it passes in
sprockets-rails 2.3
as it compiles the file on demand.You can checkout from the commit and run specs.
I expected that if you have
assets.compile = true
it will never run precompilation and alwayscompile assets on demand.
Am I understanding something wrong here?
The text was updated successfully, but these errors were encountered: