Update to Jasmine 2.0 about jasmine-rails

[searls]

Yup. A great many people are going to want to stay on 1.x until various helpers and plugins are upgraded. Additionally, the API made BC-breaking changes and so a straight upgrade may not be desirable in the near-term unless we make it configurable. On my radar but I'm not in a rush to do it or merge in a PR that merely upgrades.

On Tue, Dec 31, 2013 at 1:36 PM, Joe Lencioni [email protected]
wrote:

Jasmine 2.0 is out now (release notes).

Reply to this email directly or view it on GitHub:
#93

[jeromedalbert]

The main plugin I use, jasmine-jquery, has upgraded to Jasmine 2.0. I could not make jasmine-rails work with it, so I have falled back on the jasminerice gem at the moment (wished I hadn't though, since it is not maintained any more).

I think the "until various helpers and plugins are upgraded" stage has already happened now.

[searls]

Yup, it's time to figure out how to add support. Going to keep this ticket open as the "add jasmine 2 support" thread. My goal:

• Make everything in jasmine-rails compatible with the jasmine-core gem's API updates for version 2 (fingers crossed that they didn't change much, I haven't looked)
• Add a testbed that specifies a version of jasmine at or above 2.0.0 and get it into CI
• Relax the jasmine-rails gem's dependency on jasmine-core from jasmine-core ~> 1.3 to something that'll allow both jasmine 1 & 2 without incident.
• New users going forward should get 2 by default, old users will have to bundle update.

I was thinking this was going to be hard at first, but then realized that we can rely on bundler here (I had completely forgotten we were pulling in Jasmine itself from essentially an assets gem)

[searls]

Closed by 25d7667 and landed as 0.6.0