Feedback on Expandable hovers for JavaScript and TypeScript

Type: Feature Request

Should you show function overloads on hover expansion ?

e.g. for `Url.parse` :

Initial hover :

```typescript
function parse(urlString: string, parseQueryString: true, slashesDenoteHost?: boolean | undefined): Url.UrlWithParsedQuery (+3 overloads)
...
```

Hover expanded :

```typescript
function parse(urlString: string): UrlWithStringQuery;
function parse(
urlString: string,
parseQueryString: false | undefined,
slashesDenoteHost?: boolean,
): UrlWithStringQuery;
function parse(urlString: string, parseQueryString: true, slashesDenoteHost?: boolean): UrlWithParsedQuery;
function parse(urlString: string, parseQueryString: boolean, slashesDenoteHost?: boolean): Url;
...
```

VS Code version: Code 1.103.2 (6f17636121051a53c88d3e605c491d22af2ba755, 2025-08-20T16:45:34.255Z)
OS version: Linux x64 6.8.0-55-generic
Modes:

The issue provides a TypeScript/JavaScript hover example but names no source file, test, or implementation entry point. Start by locating the language-service hover handling and existing hover expansion tests, then verify that expanding a function hover exposes its overloads while the initial hover remains concise.

Written by the indexing model from the issue text.