-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
feat(NODE-2751): add arrayFilters builder to bulk FindOperators #2820
Merged
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
e507a63
feat(bulk): add arrayFilters builder to bulk FindOperators
emadum 123e0b4
fix min version on test
emadum 055bb7c
cleanup
emadum 0a85e9b
Merge remote-tracking branch 'origin/4.0' into NODE-2751/bulk-arrayfi…
emadum 77bd4bc
review feedback
emadum 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.
just a note: the
property
assertions can take the property name and value to compare directly, so this line is equivalent toexpect(events[0]).to.have.property('commandName', 'update')
; and if you go a step further and use thenested
keyword, you could sayexpect(events).to.have.nested.property('0.commandName', 'update')
these are personal preferences, I just wanted to make you aware of the options in case any of them appeal to you
also be careful with the
length
assertion, since it can't be reliably chained in all cases (e.g., you can't chain it offa
), so chai's own docs recommend to uselengthOf
as a general rule, since that does work exactly as expected in all cases