Compiled Assets not compiling unless body=false #315

wchenvr opened this Issue Jan 9, 2013 · 4 comments


None yet
4 participants

wchenvr commented Jan 9, 2013

So my company's test suite, when we upgraded from Jasmine 1.2.0 to the current 1.3.1, various javascript files were not being compiled into the asset pipeline, and the .erb files were being loaded, instead of the compiled js files, and we saw that certain files were not being loaded from the //= loads.

We fixed the issue by adding body=false in the jasmine.yml file, ie, assets/application.js?body=false.

I'm not sure if this behavior is correct or not, but I wanted to point it out, since in the previous version this behavior was not occurring.


ragaskar commented Jan 9, 2013

Thanks for the report. I have a feeling this is related to this other issue: pivotal/jasmine-gem#125 ... I'll try to look into it this weekend.


ragaskar commented Jan 19, 2013

Please see if jasmine-gem HEAD fixes this for you, as the asset mapping behavior has been reverted.


infews commented May 27, 2013

Is this still an issue? Can we close?


slackersoft commented Oct 2, 2013

This should be fixed in 2.0. Please take a look and let us know if this is still an issue

slackersoft closed this Oct 2, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment