To @peterflynn

An alternative to this could be a new CollectionUtils.some function that could call Object.keys().some() or use a for loop and break it if the callback return true, to make a function to loop over Objects similar to Array.some. Reference: https://developer.mozilla.org/en-US/docs/JavaScript/Reference/Global_Objects/Array/some

I've been using Array.some a lot more lately and it seems useful to have a return value, so I removed the break in forEach and added a new some function, which also makes it more consistence with the Array functions.

@TomMalbran done reviewing. Two comment nits plus this bigger question about whether we want to rename the API. We should probably wait a day or so to see if others chime in on that.

It seems like I missed several cases when switching $.each with forEach where the loop broke. This fixes one of those cases, since it needs CollectionUtils.some to work.

@peterflynn It's been a few days, and nothing happened, should we just leave like it is. The names make sense since the functions work for any collection, and JavaScript already implements different APIs with the same names.

Clarifying title (was: "Break the CollectionUtils.forEach loop if the callback returns false")

@peterflynn Great, I am glad that this is finally merged :) I know it shouldn't be used for arrays, but it is possible. It would work great when the object could be either an array or an object. Thanks for changing the name, this pull went from breaking the loop to creating a new method.

Yeah -- thanks for generalizing it that way btw. We will definitely have more places to use this :-)