-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
Support arrays in t.like() assertion #3185
Merged
Merged
Changes from 5 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
c45e837
tests(`t.like`): add case from #2627
tommy-mitchell c9a7a21
chore: merge changes from #3023
tommy-mitchell a50b1c8
feat: update `isLikeSelector` for `Reflect.ownKeys().length`
tommy-mitchell 162ecdb
refactor: simpler `isLikeSelector` solution
tommy-mitchell 7627404
tests: add array cases
tommy-mitchell 13f44c1
Additional test cases
novemberborn dc31ce3
Update documentation for t.like()
novemberborn 0510ff1
Merge branch 'main' into fix-t-like-arrays
novemberborn File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the desired behavior, or should
t.like()
only support arrays as properties on an object?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now you've opened a can of worms!
If I understand / remember correctly, the second argument recursively selects the entries of the first argument which are then compared against the second. So for objects
{a: 1, b: 2}
and{a: 3}
we compare{a: 1}
with{a: 3}
. Swap the arguments and we compare{a: 3, b: undefined}
with{a: 1, b: 2}
.For arrays then we can only compare the indexes for which the selector has a value:
[1, 2]
and[3]
compares[1]
with[3]
. Swap the arguments and we compare[3, undefined]
with[1, 2]
.I think that's all consistent enough and so it'd be fine to support arrays as top-level arguments. What do you think?