Signal inputs not getting highlighted on mouse over in element
Which @angular/* package(s) are the source of the bug?
language-service
Is this a regression?
No
Description
Signal inputs are not getting highlighted on mouseover and also it is not navigating to the source on ctrl click on it
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: 17.1.0
Node: 18.16.0
Package Manager: pnpm 8.7.0
OS: darwin arm64
Angular: 17.1.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, localize, material
... material-moment-adapter, platform-browser
... platform-browser-dynamic, router, service-worker
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1701.0
@angular-devkit/build-angular 17.1.0
@angular-devkit/core 17.1.0
@angular-devkit/schematics 17.1.0
@angular/fire 16.0.0
@angular/pwa 17.0.1
@schematics/angular 17.1.0
rxjs 7.8.1
typescript 5.2.2
zone.js 0.14.2
Anything else?
No response
What version of the Angular extension are you using?
Also ran into this on ALS Version 17.1.0
Attempting to go to definition via F12 results in No definition found for 'name', and no tooltip on hover.
However, attempting to assign an incorrect type does yield the expected error.
We see the same behavior after upgrading to 17.1.0 as well.
This should be resolved as of recent language service releases.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.