microsoft / microsoft/TypeScript
Support IntelliSense while writing JSDoc @ link tags
Open
Nobody has claimed this yet.
Experience Enhancement
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Suggestion
🔍 Search Terms
- jsdoc
@link- suggest / suggestion
- complete / completions
- IntelliSense
⭐ Suggestion
Enable IntelliSense inside JSDoc @link tags.
As precedent, we already support IntelliSense for @param parameters
📃 Motivating Example
/**
* {@link } <- Trigger suggest here
*/
const foo = 12
💻 Use Cases
This would help significantly while writing @link tags
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating the existing IntelliSense path for JSDoc @param parameters and the language-service completion entry point, then trace how an empty {@link } position is handled. Done means suggestions appear at the demonstrated position, with regression coverage for JSDoc @link completions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100