Skip to content

Conversation

@mlewand
Copy link
Contributor

@mlewand mlewand commented Jul 13, 2015

I can see that some time ago in e1090c3 there was a change where you started using jQuery.uniqueSort rather than jQuery.unique.

This change was not reflected in selector-native.js file, thus exception reported in #2466.

@mlewand
Copy link
Contributor Author

mlewand commented Jul 13, 2015

I've sent CLA after sending this PR. Will bot update the label correctly?

@dmethvin
Copy link
Member

As long as you signed with the same name and email as the commit it should be fine. If new commits are pushed to this PR it will do the check again, so hold on and let's see if any are needed.

Great catch by the way!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the "method" is actually context-free, I'd rather not introduce a reliance upon this. jQuery.unique = jQuery.uniqueSort or var uniqueSort = function …; jQuery.extend({ …, unique: uniqueSort, uniqueSort: uniqueSort, … }) would be better. Other than that, though, LGTM!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good, fix applied with daec351.

@mlewand
Copy link
Contributor Author

mlewand commented Jul 14, 2015

Is there anything more I can do for this PR?

@gibson042
Copy link
Member

Nope; we're all set.

@gibson042 gibson042 closed this in bf591fb Jul 14, 2015
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants