Use more specific Go to Type Definition message than "no type definition found" on literal values

[JoshuaKGoldberg]

TS Template added by @mjbvz

TypeScript Version: 4.6

Search Terms

• definitionAndBoundSpan
• definitions
• f12

---

Asking VS Code to go to type definition on a primitive such as true or "hello" in TypeScript gives the general No type definition found for '{0}' message:

It would be a little more accurate -and less misleading in the case of a user misclicking when they'd meant to select something else- to give an error message tailored to the value in question being a literal.

How about... '{0}' is the built-in {1} type, where {1} would be boolean, string, etc.?

I'd be happy to send this PR myself. 🙂

[mjbvz]

Moving to TS as I think this information would have to come from TS Server

In these cases, clients currently just get back an empty response for definitionAndBoundSpan