Option: fix should.js .eql() behaviour #1297
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Making Option.value a private field broke should(Option).eql() behaviour. See: getodk#1287 / 5ef4c72 Closes getodk#1296
There was a problem hiding this comment.
I've added more tests - to use the same test cases against chai & node's built-in assert module. I think these will be helpful to avoid breaking anything when/if doing incremental migration away from should.js.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Making
Option.valuea private field brokeshould(Option).eql()behaviour.See: #1287 / 5ef4c72
Closes #1296