Closed MichaelHoste closed 11 years ago
Thanks for the bug report. Happily, I was able to pull in jasmine-rails
and let it take over the asset compilation (this wasn't possible in the past) so Jax is now less tightly coupled to Jasmine. Now I want to run some additional tests before pushing a new release.
I finally migrated to 3.0.0.rc2 and I had this error when loading a page :
It seems related to https://github.com/searls/jasmine-rails/issues/19
Forcing 'jasmine' 1.3.0 in my Gemfile works but maybe something must be done in the Jax dependencies to avoid this specific issue.