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
ng lint complains about pipe async in html files #4351
Comments
@victornoel the issue is probably with codelyzer. https://github.com/mgechev/codelyzer |
Specifically, talked about here: mgechev/codelyzer#190 |
@deebloo @delasteve thanks both of you. Reading the aforementioned issue I don't get if there is a solution to this problem and what is it… The issue was closed without fixes committed apparently… |
Heya @victornoel, this problem is not solvable from the CLI side. Linting uses As far as I can tell from mgechev/codelyzer#190 there might be a workaround, but that's all. Perhaps you can open a new issue there? |
@filipesilva Thanks, So for the record, from what I understood, |
Actually it's not fixed for those interested by this :) |
Updating codelyzer to last version (3.0.0-beta.3 at this moment) makes linting passing. |
Today I have tried it with codelyzer@3.0.0 and tslint@5.1.0 and the error still appears.. |
It is not fixed on codelyzer To "fix" this, do what it wants you to do. Aka, put the property public async: any; |
V |
If I put an "elvis" operator like this: |
Is there a way to disable codelyzer or tslint from running on an HTML file? From what I can tell, using an HTML comment does not work. I'm having a similar issue and cannot fix it to get the linter to pass. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Linux Archlinux
Versions.
Repro steps.
The repo was initialised with angular-cli, didn't change tslint settings, basically it concerns html files where this kind of code appears:
The log given by the failure.
The text was updated successfully, but these errors were encountered: