Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1030985
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T13:51:27+00:00 2026-05-16T13:51:27+00:00

A common pattern within jQuery is a method that takes a callback which is

  • 0

A common pattern within jQuery is a method that takes a callback which is passed an element of an array and its index within that array. However, it seems completely random which argument comes first. For example, from the jQuery docs at http://api.jquery.com:

  • jQuery.each( collection, callback(indexInArray, valueOfElement) )
  • .each( function(index, Element) )
  • jQuery.map( array, callback(elementOfArray, indexInArray) )
  • .map( callback(index, domElement) )
  • jQuery.grep( array, function(elementOfArray, indexInArray), [ invert ] )
  • .filter( function(index) )

In three cases (jQuery.each, .each, .map) the index comes first. In the other two (jQuery.grep, jQuery.map) the element comes first. I know the api is now set, but it seems like a gross inconsistency to me.

Is there a pattern I’m missing or is this just random? Should this be fixed or should I just shut up and memorize them?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T13:51:27+00:00Added an answer on May 16, 2026 at 1:51 pm

    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.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a common pattern which Im sure there must be a built-in array
A common pattern with templated classes is that template argument is typedef'ed inside the
I'm finding a common pattern during my WP7 development. Something takes a long time
A common pattern in C++ is to create a class that wraps a lock
I'm running into a common pattern in the code that I'm writing, where I
I've noticed that a common pattern I use is to assign SomeClass.__init__() arguments to
The template method pattern provides that the abstract base class has a not overridable
Is it a common pattern/idiom to use free functions as pseudo-constructors to avoid having
This is becoming a common pattern in my code, for when I need to
I'm working with a fairly common pattern - a page opens a child window

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.