Incorrect asset path in Rails 4 beta about jasmine-rails

[searls]

That's new and surprising, AFAIK. So it works for you in Rails 3, but not 4, I surmise?

[curthasselschwert]

This is a brand new app, so I haven't tried it in 3. Everything else works fine. I'm not familiar enough yet with the asset pipeline to understand exactly what's going on. I've been trying to work through the Rails source, but no luck yet. I'll create a sample app to look at.

[searls]

Can you verify whether this is still an issue in the latest jasmine-rails release 0.3.0?

[jleo3]

I can verify that jasine-rails version 0.3.3 works well with rails version 4.0.0.beta1. I'm using it in a project now and having no issues.

[RKushnir]

I'm having this issue on Rails 3.2. It renders path as /specs/assets/....

upd. It seems this has been fixed in Rails 4.0.0(rails/rails@445f14e). Any suggestions what to do on 3.2?

[searls]

@RKushnir I recommend you check out the test script, as it seems to be working fine there. Perhaps your config is off?

[RKushnir]

@searls Thanks, I figured the issue was with the backport version of sprockets-rails I was using.

[timdiggins]

@RKushnir I'm having same problem with jasmine-rails & sprockets-rails (backpoint). Can you point me to your solution?

[RKushnir]

@red56 Check this out rails/sprockets-rails#114. As there doesn't seem to be any reaction, you can create your own fork that incorporates the specified patch.