Skip to content
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

fix(forkJoin): fix forkJoin typings for forkJoin(Observable<any>[]) #3436

Merged
merged 1 commit into from
Mar 15, 2018

Conversation

benlesh
Copy link
Member

@benlesh benlesh commented Mar 15, 2018

Solves an issue where we were hitting the wrong typings for forkJoin if passed an Array of observables.

export function forkJoin<T>(sources: Array<ObservableInput<T>>): Observable<T[]>;
export function forkJoin<T>(...sources: Array<ObservableInput<T>>): Observable<T[]>;
export function forkJoin<T>(v1: ObservableInput<T>): Observable<T[]>;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not exactly sure, but prolly this could be go line 10 instead?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I agree.

@coveralls
Copy link

coveralls commented Mar 15, 2018

Coverage Status

Coverage remained the same at 97.544% when pulling ff8fd44 on benlesh:forkJoin-shennanigans into b61d8ce on ReactiveX:master.

@benlesh
Copy link
Member Author

benlesh commented Mar 15, 2018

It now also updates typings to be a little nicer for people passing an array in.

@lock
Copy link

lock bot commented Jun 6, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants