-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
no-implicit-any-catch
throws an error
#122
Comments
We have a similar situation, but I'd like to add that even with a disabling comment for this |
We have a similar situation. We had to turn this rule off while we wait for a fix. Example: of(1).pipe(
catchError((err) => {
return of(2);
}),
); Log:
|
When
no-implicit-any-catch
encounters acatchError
statement without any types we end up getting an error. See cartant/eslint-plugin-etc#63 as this happens in this repository as well.It appears cartant/eslint-etc#12 fixes the problem for us. Hoping we could get a review and merge on that PR? Once I used the contents of that PR it resolved this error for us. We'd like to enable the
no-implicit-any-catch
rule but need this merged to do so.The text was updated successfully, but these errors were encountered: