Why are jQuery's callback arguments inconsistent?

时光怂恿深爱的人放手 提交于 2019-11-28 20:22:39

It is not totally random. Because :

$.map( $('selector'), function(el, index) { /* element (DOMElement) is first, index optional */ } );
$('selector').map(function(index) { /* 'this' (DOMElement) is first.... index optional */ });

See the pattern? The second example has a second argument, but it is only passed by convenience, and it is the same as this.

The pattern is that the first argument is always "more" important than the second, and the last argument should be the least important (the "more optional"). So you don't need to specify all the least important arguments if you only need one. And in the case of $(...).each, often you won't even need any argument, because this is only what you want.

That's frustrated me also at times -- $.each is the one that I always mess up.

I think it's due to different people/teams working on different parts of the framework. It's a community-driven framework, so nobody probably caught it early on and now that the framework is so wide-spread, they can't fix it without breaking 35% of all the sites on the Internet.

I don't think it will be fixed -- at least that's my opinion/attitude. I'm just going to have to commit them to memory and hope for the best!

Since Javascript lets you ignore parameters that you aren't using (i.e., you can define a callback function which takes only one parameter, even if it will be called with two), generally, the first parameter is the one you are mostly likely to be using. (Actually, the this varaible is usually the data item you'r most likely to use, followed by the first parameter, etc)

According to https://learn.jquery.com/using-jquery-core/iterating/

A word of warning: $.map() switches the order of callback arguments [when compared to $().map, $each() and $().each()]. This was done in order to match the native JavaScript .map() method made available in ECMAScript 5.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!