You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a separate .html file (via templateUrl in the @Component decorator) instead of an inline template, no-access-missing-member doesn't complain about using properties (e.g. in an *ngIf expression) that don't exist in the class definition.
To reproduce:
Use Angular CLI to create a new project, e.g.: ng new test-playground
Edit the generated src/app/app.component.html to add *ngIf="foobar" to the h1 tag. (Do not add a foobar property to the class)
Run ng lint. The output will be All files pass linting. It seems to me that it should complain about the use of the foobar property that does not exist.
The text was updated successfully, but these errors were encountered:
When using a separate
.html
file (viatemplateUrl
in the@Component
decorator) instead of an inline template,no-access-missing-member
doesn't complain about using properties (e.g. in an*ngIf
expression) that don't exist in the class definition.To reproduce:
ng new test-playground
src/app/app.component.html
to add*ngIf="foobar"
to theh1
tag. (Do not add afoobar
property to the class)ng lint
. The output will beAll files pass linting.
It seems to me that it should complain about the use of thefoobar
property that does not exist.The text was updated successfully, but these errors were encountered: