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

fixes for typescript 2.4 #2780

Merged
merged 1 commit into from
Aug 3, 2017
Merged

fixes for typescript 2.4 #2780

merged 1 commit into from
Aug 3, 2017

Conversation

evmar
Copy link
Contributor

@evmar evmar commented Aug 3, 2017

TypeScript 2.4 is more strict about assignability with generics,
and in some cases (when calling a generic function) it will infer
that the generic parameter is <{}> rather than the that rxjs
typically wants.

Fix this by explicitly passing in the cases where compilation
fails.

Description:

Related issue (if exists):

@rxjs-bot
Copy link

rxjs-bot commented Aug 3, 2017

Messages
📖

CJS: 3175.7KB, global: 588.9KB (gzipped: 108.6KB), min: 138.0KB (gzipped: 29.1KB)

Generated by 🚫 dangerJS

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.736% when pulling 6f96629 on evmar:ts24 into b8a324f on ReactiveX:master.

TypeScript 2.4 is more strict about assignability with generics,
and in some cases (when calling a generic function) it will infer
that the generic parameter is <{}> rather than the <T> that rxjs
typically wants.

Fix this by explicitly passing <T> in the cases where compilation
fails.
@coveralls
Copy link

coveralls commented Aug 3, 2017

Coverage Status

Coverage remained the same at 97.736% when pulling 6f96629 on evmar:ts24 into b8a324f on ReactiveX:master.

@benlesh benlesh merged commit d2a32f9 into ReactiveX:master Aug 3, 2017
GulajavaMinistudio added a commit to GulajavaMinistudio/rxjs that referenced this pull request Aug 4, 2017
fix(compilation): compile under typescript 2.4 (ReactiveX#2780)
hermanbanken pushed a commit to hermanbanken/RxJS that referenced this pull request Aug 7, 2017
TypeScript 2.4 is more strict about assignability with generics,
and in some cases (when calling a generic function) it will infer
that the generic parameter is <{}> rather than the <T> that rxjs
typically wants.

Fix this by explicitly passing <T> in the cases where compilation
fails.
@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.

4 participants