We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Seems to be a problem with object key ordering.
// This fails: expect( [ { type: types.COMPLETE_TODO, id: 0 }, { type: types.CLEAR_COMPLETED }, { type: types.ADD_TODO, text: 'Write more tests' } ].reduce(todos, [ { id: 0, completed: false, text: 'Use Redux' }, { id: 1, completed: false, text: 'Write tests' } ]) ).toEqual([ { text: 'Write more tests', completed: false, id: 2 }, { text: 'Write tests', completed: false, id: 1 } ]) // Changing the key order in the argument of `toEqual` as follows passes: expect( [ { type: types.COMPLETE_TODO, id: 0 }, { type: types.CLEAR_COMPLETED }, { type: types.ADD_TODO, text: 'Write more tests' } ].reduce(todos, [ { id: 0, completed: false, text: 'Use Redux' }, { id: 1, completed: false, text: 'Write tests' } ]) ).toEqual([ { id: 2, completed: false, text: 'Write more tests' }, { id: 1, completed: false, text: 'Write tests' } ])
Could be due to this issue in the new is-equal library
The text was updated successfully, but these errors were encountered:
This is now fixed and released in is-equal v1.3.1. Sorry about that!
is-equal
v1.3.1
Sorry, something went wrong.
Yep, all good now. Thanks @ljharb.
No branches or pull requests
Seems to be a problem with object key ordering.
Could be due to this issue in the new is-equal library
The text was updated successfully, but these errors were encountered: