JSDoc tags not parsed when a type may be present

🔎 Search Terms

jsdoc links missing in possible type position

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about JSDoc

⏯ Playground Link

https://www.typescriptlang.org/play/?#code/MYGwhgzhAEDC0G8BQBfJB6AVJp1PQAEAXACwCcB7AdxgQJAEsA7AazjT3SQDMBXJ4EQYUm0LJnSxYACgCUiVEA

💻 Code

class C {
}
/**
 * @throws {@link C}
 */
function /**/CC() {
}

🙁 Actual behavior

TypeScript does not resolve {@link C}.

Hover on the playground shows:

@throws — {
@link — C}

🙂 Expected behavior

TypeScript should resolve {@link C}

Hover on the playground should show this (or even better rendered links like it does in vscode)

@throws — {@link C }

Additional information about the issue

Originally reported in https://github.com/TypeStrong/typedoc/issues/2993

Inizia con il link fornito a TypeScript Playground e con l’esempio JSDoc contenente @throws {@link C}. Traccia il modo in cui vengono analizzati i tag JSDoc quando può essere presente un tipo; il lavoro è completato quando il link viene risolto in C e l’hover di Playground mostra il contenuto del link invece di separare @link da C.