jquery-migrate
jquery-migrate copied to clipboard
jquery
A development tool to help migrate away from APIs and features that have been or will be removed from jQuery core
jQuery Migrate does two things: 1. Fills in removed APIs, warning when used. 2. Warns about deprecated APIs that still exist. It makes sense to differentiate these two for a...
Migrate warns against `.removeAttr()` called on boolean attributes as this used to set the associated property to `false` but it doesn't do so anymore since jQuery 3.0.0. However, this is...
It got deprecated in jQuery 3.3.0: * https://api.jquery.com/jQuery.proxy/ * https://blog.jquery.com/2018/01/19/jquery-3-3-0-a-fragrant-bouquet-of-deprecations-and-is-that-a-new-feature/
When calling `$(el).data()`, the received object contains camel-cased keys, this fixes issue #436
Currently this migration script fixes only `$.data()` calls, but `$.fn.data` still have the incompatibility with automatic camelCase conversion. ```js // el: var data = $(el).data(); // data: {myProp: 'test'} assert(data['my-prop']===test)...
The release script currently updates the `package.json` file manually which leaves `package-lock.json` with the old version. Switch the release script to use `npm version`, it's probably easiest to use the...
See discussion in https://github.com/jquery/sizzle/issues/293 . They aren't being removed in jQuery 3.0 but we should warn since they are being deprecated.
My site uses `$.ajaxSettings.traditional = true`, and we're working on upgrading to jQuery 3 now. The migrate script is showing a warning when I use `$('form').serialize()` because the implementation within...
We should verify that Migrate meant to aid migration from jQuery n-1 to n passes as much as possible from the jQuery n-1 test suite. One idea is to commit...