Go-to-definition should only show relevant definitions when value & type have same name

🔎 Search Terms

"go to definition", "same identifier", "value", "type"

🕗 Version & Regression Information

Always was the case, AFAIK

⏯ Playground Link

https://www.typescriptlang.org/play?#code/C4TwDgpgBMULxQN4F8oFgBQmDGB7AdgM6ywIrpYYBmArvtsAJYFRUAUAhgE4DmAXDACUSKKgD0YqD1yN8PGLigATCFVmMmLFgANg2qAAsIXCIGgCKYwBuEQstXrNRKLipQARrmAGoAWhjhoDnwlKEsOABsaaF1tABooCGt8GANcGh5vMMjovShsIPxPd2gaQggQ2RTGWzBwjmwIAWBCbF8Eri5cLigAFQBlACYAdgAWAE4BAHJgSagTKmNbYEUOUIio+LcaWGri2XlS8qgOW1XQSENjCAA6KAARRhCQNKgAWwggqGmAlxhJgH5MJggA

💻 Code

type t = {} 

const t = {} 

function f(arg: t) { } // going to definition on `t` here​ gives definitions of both - type and value `t`, even though value `t` cannot be used in this place: tsc - error TS2749: 't' refers to a value, but is being used as a type here. Did you mean 'typeof t'?

🙁 Actual behavior

"Go to definition" on a param type t shows 2 definitions - value & type which have same name - even though the value's definition is completely irrelevant.

🙂 Expected behavior

"Go to definition" shows only relevant definition of type t

Additional information about the issue

No response

Inizia con la riproduzione in Playground e la richiesta go-to-definition per t in function f(arg: t). Traccia come il servizio del linguaggio risolve le definizioni quando un tipo e un valore condividono lo stesso nome; il lavoro è completato quando il risultato contiene solo la definizione del tipo, preservando le definizioni rilevanti negli altri contesti.