-
Notifications
You must be signed in to change notification settings - Fork 20.5k
Event: Move .bind() and .delegate() to deprecated #2624
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case you haven't heard, I'm not a fan of this method.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, it's confusing. We could deprecate it in 3.0 & remove in 4.0 perhaps?
|
LGTM. Tests would be nice but since you're just moving code around it's not a blocker here. BTW, we've had Should we duplicate a few basic |
|
I don't mind adding tests to this PR, just some basic sanity tests that are copies of what we already have but calling the deprecated methods. And we already have an empty |
|
In my opinion, anything more than equal( jQuery.fn.on, jQuery.fn.bind, ... );is just redundant. |
|
@timmywil They're not equal, |
|
Of course. It's been a long time since I've used them. :P |
|
Tests are added, are we good to go? |
|
Should be good to go. Just added the Migrate issue |
|
Okay, merging |
Fixes #2288
At the moment we don't have any tests at all for .bind() and .delegate(), it seems like we would at least want a sanity check for them. At the very least they should be tested in Migrate.
While I'm in here I'm wondering if we should deprecate anything else in the aliases.