-
Notifications
You must be signed in to change notification settings - Fork 27.3k
Compiler should error on unknown structural directives #37322
Copy link
Copy link
Closed
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: compilerIssues related to `ngc`, Angular's template compilerIssues related to `ngc`, Angular's template compilerarea: coreIssues related to the framework runtimeIssues related to the framework runtimecore: directive matchingcore: ng-template and *microsyntaxcross-cutting: typesstate: confirmed
Milestone
Description
Metadata
Metadata
Assignees
Labels
P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgentAn issue that is relevant to core functions, but does not impede progress. Important, but not urgentarea: compilerIssues related to `ngc`, Angular's template compilerIssues related to `ngc`, Angular's template compilerarea: coreIssues related to the framework runtimeIssues related to the framework runtimecore: directive matchingcore: ng-template and *microsyntaxcross-cutting: typesstate: confirmed
Issue an warning when compiling a template that do not match an structural directive selector.
Relevant Package
This feature request is for @angular/core
Description
The compiler completely ignore an selector like *myStructuralDirective without warning if it do not match any directive. This turns difficult to see that we are doing something wrong.
Describe the solution you'd like
If the selector in the template for an structural directive do not match any directive, show an warning about possible wrong usage.
Describe alternatives you've considered
I don't see alternatives.