-
Notifications
You must be signed in to change notification settings - Fork 27.5k
fix(equals): {} and [] should not be considered equivalent #2852
Conversation
If you accept #2775 first, it should clean up the changelog. Sorry again for the crossover. |
Code LGTM. This issue reminds me of this 😄 |
Actually, this is all expected if you know how JS works. So long you know what |
PR Checklist (Minor Bugfix)
|
@appsforartists - can you sign the CLA please? |
I think I already have, but I signed it again just-in-case.
On Wed, Jul 17, 2013 at 6:45 AM, Pete Bacon Darwin <notifications@github.com
|
@appsforartists one more thing - would you mind squashing commits? So there is only one commit in the pull request (following commit message guidelines)? |
angular.equals was returning inconsistent values for the comparison between {} and []: angular.equals({}, []) // true angular.equals([], {}]) // false Since these object are not of the same type, they should not be considered equivalent.
@pkozlowski-opensource I just ran |
this landed long time ago as 1dcafd1 but the PR never got closed. thanks! |
angular.equals was returning inconsistent values for the comparison between
{} and []:
Since these object are not of the same type, they should not be considered
equivalent.
Fixes #2851