fix(language-service): correctly handle host directive inputs/outputs#48147
fix(language-service): correctly handle host directive inputs/outputs#48147crisbeto wants to merge 1 commit intoangular:mainfrom
Conversation
There was a problem hiding this comment.
The || '' here is weird, but I don't know the context behind why the language service requires a selector for all directives, even though directives can be declared without selectors.
There was a problem hiding this comment.
Before the directive composition, a directive couldn't match anything unless it had a selector. I think the correct thing would be to make this optional now. Can you add a TODO or make the change if it's easy enough?
There was a problem hiding this comment.
I left a TODO for myself. I'll send a follow-up PR once this one goes in.
24e4803 to
4e7ddbc
Compare
Adds some logic to correctly handle hidden or aliased inputs/outputs in the language service. Fixes angular#48102.
4e7ddbc to
0d27a64
Compare
|
This PR was merged into the repository by commit fd2eea5. |
This is a follow-up from angular#48147. Changes the `DirectiveSymbol.selector` to be nullable since it's possible to have directives without a selector.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
…angular#48147) Adds some logic to correctly handle hidden or aliased inputs/outputs in the language service. Fixes angular#48102. PR Close angular#48147
Adds some logic to correctly handle hidden or aliased inputs/outputs in the language service.
Fixes #48102.