go to this link:-http://nfriedly.com/techblog/2009/06/advanced-javascript-objects-arrays-and-array-like-objects/…

I would take a look at your design and see if objectArray could instead be an Object, and not an Array. If so, I’d change it’s name to objectLookup, and then finding a module with “attendanceindex” is O(1).

   var objectLookup = {
       attendanceindex :
         {
	        moduleKey: "attendancecalendar",
	        iframe: true,
	        innerWidth: 500,
	        innerHeight: 350,
	        opacity: 0.35,
	        scrolling: false,
	        identifierType: "href"
	 },
         // ...rest of contents of objectArray
    };

    //then later..
    var winner = objectLookup.attendanceindex;

There’s no “quick” way to do it, you’d just need to loop through the entire list and check each one until you find it:

var winner;
for(var i=0; i< detailsArray.length; i++) {
  if(detailsArray[i].moduleKey === "attendanceindex") {
    winner == detailsArray[i];
    break;
  }
}

Note, I said “quick” in quotes because in reality even with 1000 items in the array it took 0.005 seconds on my laptop (I tested it).

     var detailsArray = [
        {
            moduleKey: "attendancecalendar",
            iframe: true,
            innerWidth: 500,
            innerHeight: 350,
            opacity: 0.35,
            scrolling: false,
            identifierType: "href"
        },
        {
            moduleKey: "attendanceindex",
            iframe: true,
            innerWidth: 500,
            innerHeight: 350,
            opacity: 0.35,
            scrolling: false,
            identifierType: "href"
        }
        //etc.
    ];

——
How would I find the object whose moduleKey is “attendanceindex”?
Thanks

Yea, those are good points, both about arrays not getting their own type and forEach loops hitting inherited items as well as local items. It’s handy when you want those inherited items to be in the loop though.

Similarly, live collections can be really handy, as long as you realize they’re live

What’s really unfortunate is that for in loops are deceptively not forEach loops. They iterate over every key in the object on the right side of the in without regard to whether that key is actually part of that object! I don’t really see an issue with the for in loops using ‘two’ as an index though, it seems proper. For in returning prototype keys instead of objects keys though can be a real mess. =/