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
Current Behavior
The overload signatures for find don't reflect the operator's behaviour.
find
The return types are OperatorFunction<T, S> and MonoTypeOperatorFunction<T>.
OperatorFunction<T, S>
MonoTypeOperatorFunction<T>
However, the operator will emit undefined if no match is found. See this test.
undefined
Possible Solution
The return types should be OperatorFunction<T, S | undefined> and OperatorFunction<T, T | undefined>.
OperatorFunction<T, S | undefined>
OperatorFunction<T, T | undefined>
The text was updated successfully, but these errors were encountered:
chore(dtslint): add find tests
e44ade0
Closes ReactiveX#3969.
a227ed5
5a6c90f
Successfully merging a pull request may close this issue.
Bug Report
Current Behavior
The overload signatures for
find
don't reflect the operator's behaviour.The return types are
OperatorFunction<T, S>
andMonoTypeOperatorFunction<T>
.However, the operator will emit
undefined
if no match is found. See this test.Possible Solution
The return types should be
OperatorFunction<T, S | undefined>
andOperatorFunction<T, T | undefined>
.The text was updated successfully, but these errors were encountered: