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
For example, signature of Observable.of is defined as below
Observable.of
Rx.Observable.of(value, [scheduler])
and declaration is like below, accepts value or scheduler with union type definition.
static of<T>(...array: (T | Scheduler)[]): Observable<T>
which makes eventually type inference confusions like
since array now contains value:T and scheduler:Scheduler both.
While this doesn't hurt functionality at all, would be better to have way to suppress these type of complains.
The text was updated successfully, but these errors were encountered:
I will prepare PR resolves this issue partially as starting point.
Sorry, something went wrong.
fix(operator): update type definitions for union types
0a032a0
- allow multiple type parameters can be accepted for observable, operator supports array of union types closes ReactiveX#581
9d90c75
Successfully merging a pull request may close this issue.
For example, signature of
Observable.of
is defined as belowRx.Observable.of(value, [scheduler])
and declaration is like below, accepts value or scheduler with union type definition.
static of<T>(...array: (T | Scheduler)[]): Observable<T>
which makes eventually type inference confusions like
since array now contains value:T and scheduler:Scheduler both.
While this doesn't hurt functionality at all, would be better to have way to suppress these type of complains.
The text was updated successfully, but these errors were encountered: