Skip to content

fix(language-service): Provide support for protected signal inputs#68029

Draft
atscott wants to merge 3 commits intoangular:mainfrom
atscott:protectedSignalInputs
Draft

fix(language-service): Provide support for protected signal inputs#68029
atscott wants to merge 3 commits intoangular:mainfrom
atscott:protectedSignalInputs

Conversation

@atscott
Copy link
Copy Markdown
Contributor

@atscott atscott commented Apr 3, 2026

built on top of #67961 because otherwise the solution would default to using the typechecker that we're trying to remove

atscott added 3 commits April 3, 2026 15:46
Add HOST_DIRECTIVE expression identifier to TCB comments to identify host directives.
…ecker

This updates the SymbolBuilder to no longer use ts.TypeChecker internally to
build symbols for the language service. These lookups are deferred/done later
using the newly expanded template type checker API.
Protected signal inputs weren't working. now they are.
@atscott atscott marked this pull request as draft April 3, 2026 23:26
@angular-robot angular-robot bot added area: compiler Issues related to `ngc`, Angular's template compiler area: language-service Issues related to Angular's VS Code language service labels Apr 3, 2026
@ngbot ngbot bot added this to the Backlog milestone Apr 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: compiler Issues related to `ngc`, Angular's template compiler area: language-service Issues related to Angular's VS Code language service

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant