-
Notifications
You must be signed in to change notification settings - Fork 3k
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
FromEvent Docs: No overload matches this call. #7245
Comments
@demensky in the documentation it says that third argument is either or boolean or an object. If it's changed now ... Should I make ammendment in the docs and send a PR ? |
@sumitrawat10 |
demensky
added a commit
to demensky/rxjs
that referenced
this issue
Apr 9, 2023
demensky
added a commit
to demensky/rxjs
that referenced
this issue
Apr 10, 2023
demensky
added a commit
to demensky/rxjs
that referenced
this issue
Apr 11, 2023
demensky
added a commit
to demensky/rxjs
that referenced
this issue
Apr 11, 2023
jakovljevic-mladen
pushed a commit
that referenced
this issue
Apr 12, 2023
jakovljevic-mladen
pushed a commit
that referenced
this issue
Apr 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
As per the https://rxjs.dev/api/index/function/fromEvent in order to use this operator with capture option we can pass the three arguments to it.
But LSP is showing the following error.
Expected behavior
As per the documentation.
DOM EventTarget
This is an object with addEventListener and removeEventListener methods.
In the browser, addEventListener accepts - apart from event type string and event handler function arguments - optional third parameter, which is either an object or boolean, both used for additional configuration how and when passed function will be called. When fromEvent is used with event target of that type, you can provide this values as third parameter as well.
Reproduction code
Reproduction URL
No response
Version
~7.5.0
Environment
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: