-
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
Error in project with TS 2.6 and strictFunctionTypes #3031
Comments
same issue |
For the second fix option, I guess really we want |
We're experiencing the problem as well. |
I'm also running into this issue. |
The same problem for me! Any updates on this? |
the same issue. |
same issue |
also, even after using |
same issue here, can you please tell me what are the steps to fix ? I upgraded to: applying: |
To workaround this issue, you need, |
@craftytrickster yeah, I meant |
The issue in the VirtualTimeScheduler.d.ts file is there with TS 2..7.1 too. |
adding "skipLibCheck": true in tsconfig.json causes error with shared npm module,
|
As @colindekker said - the best way is to change the |
This issue is fixed in (these)
@benlesh Any idea when we might get a new alpha? I'm very new to the codebase, but I could take a swing at those issues if they're not already in progress. |
Note that this issue makes the Angular CLI command |
Is there a version of RxJS 5.x not experiencing this? |
It might be due to source in my project Antares, but this error that seems to come from inside of RxJS.. CC @alexjoverm - this is from a module I made from your (very nice) starter kit from a few days ago.
|
I believe this should be resolved. If not, please feel freely file new issue. |
RxJS version: 5.5.2
Code to reproduce:
In
tsconfig.json
:Expected behavior:
Compiles successfully.
Actual behavior:
Compiler error:
Additional information:
Workaround: disable
strictFunctionTypes
OR enableskipLibCheck
I believe this is happening because
work
is not defined as a method (rather, it's defined as a property), so its parameters are checked contravariantly. If it was defined as a method, the parameters would be checked covariantly.This could be fixed by defining
work
as a method in both classes, or defining it as(this: AsyncAction<T>, state?: T) => void
inVirtualAction
.The text was updated successfully, but these errors were encountered: