Closed mattbrictson closed 8 years ago
I ran the tests against Rails 4.0.13, 4.1.14, and 4.2.5. For 4.2.5, I also tested with sprockets-rails 2.3.3 and 3.0.0. Everything checks out!
This would be nice to see merged in - I recently tried pulling this into a Rails 5 beta 1 app, and got the above error. Thanks!
@brentd any chance we can get this merged in?
This worked perfectly, and the patch looks beautiful! :sparkles:
I think that’s great work! :+1:
Thanks @mattbrictson!
Released in v0.1.18
It seems that sprockets-rails 3.0.0 does not initialize the
app.assets
object until it runs itsafter_initialize
block. This means that xray-rails must move its initialization process intoafter_initialize
as well.The exception is the
config.assets.precompile
modifications, which must be done earlier before that array gets frozen.These changes fix the "asset pipeline is currently disabled" error when starting up a Rails app that uses sprockets-rails 3.0.0.
This fixes #61.
@brentd Could you give me some pointers on how to test this PR? I am having trouble getting
rspec
to run (maybe you could share your Gemfile.lock?). I've manually tested this patch using a Rails 4.2.5 app, but I'd like to make sure the test suite passes (and ideally test older versions of Rails and sprockets-rails as well).Edit: I got
rspec
working and the tests are passing.