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
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
No
Description
The application uses nx and @angular/core version 16.2.12, I am trying to use new features introduced in Angular version 16, specifically required inputs. When I try to do so, the component gets highlighted in my IDE with the message as I hover saying:
Missing binding for required input (name of input) of component (name of component)
Hovewer, the build is still successfull, and the application compiles successfully.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
Angular CLI: v16.2.12
Node: v18.12.1
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Required inputs are only checked when using the AOT compiler, and only if strictTemplates or at least fullTemplateTypeCheck is enabled (without those options, nested templates within a component are not type-checked, meaning that required inputs in nested templates aren't reported as well)
This is a case for me. I am very much sorry and thank you for the prompt reply. Switching the strictTemplates option to true absolutely solves my problem.
Which @angular/* package(s) are the source of the bug?
core
Is this a regression?
No
Description
The application uses nx and @angular/core version 16.2.12, I am trying to use new features introduced in Angular version 16, specifically required inputs. When I try to do so, the component gets highlighted in my IDE with the message as I hover saying:
Hovewer, the build is still successfull, and the application compiles successfully.
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: