I'm doing a new project (Angular 18) based on an old project (Angular 14), then i have no idea if it worked in any versions after the creation of Signals.
Description
When creating a class with the directive decorator and adding inputs that are signals, extending it in another component and then trying to use that component in the HTML, the inputs from the base class are not visible.
Bug Type
This bug prevents the VSCode autocomplete/sugestion to show the inputs from the extendend directive and the possible values in it.
This code was tested in Webstorm too and the autocomplete/sugestion worked fine (not by be, but a moderator from Angular discord, i dont use Webstorm).
Expected behavior
All signal inputs from extended directives should be recognized when using autocomplete/sugestion.
š bug report
Is this a regression?
I'm doing a new project (Angular 18) based on an old project (Angular 14), then i have no idea if it worked in any versions after the creation of Signals.
Description
When creating a class with the directive decorator and adding inputs that are signals, extending it in another component and then trying to use that component in the HTML, the inputs from the base class are not visible.
Bug Type
This bug prevents the VSCode autocomplete/sugestion to show the inputs from the extendend directive and the possible values in it.
Reproduction
https://stackblitz.com/edit/stackblitz-starters-bdy9gh?file=src%2Fapp%2Fbutton%2Fbutton.component.ts
This code was tested in Webstorm too and the autocomplete/sugestion worked fine (not by be, but a moderator from Angular discord, i dont use Webstorm).
Expected behavior
All signal inputs from extended directives should be recognized when using autocomplete/sugestion.
š Your Environment
Angular Version:
Extension Version:
VSCode Version:
Operating System:
Extension options: