Open michaelaird opened 11 years ago
We should definitely update the current assembly to at least v1.10.
Going forward, maybe look at a different strategy for the newer 2.x builds. I want to be able to say the jquery assembly and nuget versions should match up with jquery script versions, but it might not be practical to keep up with every change in jquery.
My understanding is that 1.{current} and 2.{current} should have identical api's but 2.{current} has a bunch of code removed that was required to support older browsers.
I'll try to spend a bit of time over the next week updating the jQuery project to 1.10.1/2.0.2.
I came across an issue today with methods on IDeferred that were deprecated in jQuery 1.7 and removed in jQuery 1.8:
see http://api.jquery.com/category/deferred-object/
The interface in both the master and cc branches seems to be the pre 1.7 api.
I'm happy to contribute an updated interface but it raises the question of which version of jQuery should Script# support? jQuery seems to be iterating quite quickly lately and being aggressive about removing deprecated api's. Should we be versioning the library (and nuget package) for each version of jQuery?
Thoughts?