-
Notifications
You must be signed in to change notification settings - Fork 235
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
check-pipe totally broken #365
Comments
Thanks for reporting the issue. There are two issues in this case:
I'll push a fix in upcoming releases. |
Similar error here:
For this line: <div *ngIf="(currentProject | async).ui.features as features"> |
@mgechev, sorry, but I can't see how this error is related to this issue. Can you explain? I searched a little more, looks like there are other issues more likely to math the errors above: #190 and angular/angular-cli/issues/6554 This issue appeared after I updated from
|
@willgm Perharps, you should simply drop rule |
@wKoza, now I got it, thanks! 🎉 |
Does anyone know if there's a way to disable this rule just for the templates that have the problem? I'd like to avoid just turning off the whole rule, since it only seems to fail in some limited situations (async pipe, inherited properties, etc.). |
You can disable the rule for the entire file by |
Thanks, I was thinking it needed to go in the actual HTML somehow. I'll try it on the component itself. |
Same thing in an HTML. This works:
this generates an error:
this is the error: |
You can disable the rule for now until we fix the issue. |
How do I disable it? |
you should simply drop option |
@mgechev could you publish an update with this guy so we can get a clean CI build again? :) |
Yes, I'll do over the weekend. Will also do some dogfooding to verify that everything is fine. |
@mgechev the issue seems not to be resolved for me:
this is the HTML code:
from package.json:
|
Closed and reported to #416 |
Since 3.1.2 check-pipe is totally broken.
The text was updated successfully, but these errors were encountered: