You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
@Griffinz: angular.equals() ignores all properties beginning with $, and all properties whose values are functions, when both arguments are objects. Therefore, I'm not quite sure what you're getting at, can you post a reproduction demonstrating your problem, or write a failing test? I think this might be a problem if they are array-like objects
...Nope, I'm wrong, it seems to work just fine with arrays.
Because the issue tracker is so packed lately, and as far as I can tell this is invalid, I think I need to close this. But if you can demonstrate a situation where this doesn't work as expected, please open another issue with a detailed reproduction. Thanks~~
With the changes to copy() from: #1875
hashkeys are no longer copied from the source. However when comparing two objects with angular.equals(o1,o2), hashkeys are still taken in to account.
Can hashkeys be ignored by equals()? Since hashkeys are omitted from copy(), the same rule should be applied to equals().
Expected behavior: angular.equals(foo, copy(foo)) === true;
The text was updated successfully, but these errors were encountered: