docs(operators): clarify that find can emit undefined
#6538
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
|
Note that the commit message (and PR title) is wrong - it's referencing |
lazarljubenovic
changed the title
filter can emit undefinedfind can emit undefined
|
My bad, was trying to multitask too much 😄 It should be easy for the merger to change the |
benlesh
approved these changes
Aug 5, 2021
|
Thank you @lazarljubenovic |
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.
Description: Was bitten by this; I expected no emission to happen if nothing is found. Thought it would be good to explicitly state the edge case in the docs, since just “it won't throw” don't really say anything about what will happen instead (nothing vs emits undefined).