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
As you can see, the MyBaseDirective is not even exported from the file, because it is kind of a private DRY solution. The MyDirective is of course declared in the main app module.
When I try to use the myInput of an <a> element...
<a[myInput]="myVar">Link</a>
...I get an error message: Can't bind to 'myInput' since it isn't a known property of 'a'.
The code itself is working fine, and if I export the MyBaseDirective, the error disappears.
Bug Type
What does this bug affect
Angular Language Service VSCode extension
Angular Language Service server
Expected behavior
The inherited inputs and outputs from a non-exported directive should be detected properly.
🐞 bug report
Is this a regression?
Not sure.
Description
I have an abstract directive with a custom input and another one that extends it:
As you can see, the
MyBaseDirective
is not even exported from the file, because it is kind of a private DRY solution. TheMyDirective
is of course declared in the main app module.When I try to use the
myInput
of an<a>
element......I get an error message:
Can't bind to 'myInput' since it isn't a known property of 'a'
.The code itself is working fine, and if I export the
MyBaseDirective
, the error disappears.Bug Type
What does this bug affect
Expected behavior
The inherited inputs and outputs from a non-exported directive should be detected properly.
🌍 Your Environment
Angular Version:
Extension Version:
VSCode Version:
Operating System:
Additional Info
Might be related? #150
The text was updated successfully, but these errors were encountered: