microsoft / microsoft/language-server-protocol
Async functions in documentSymbols and completion
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
textDocument/semanticTokens has an async modifier which can be used to distinguish def f(): ... from async def f(): .... How hard would it be to support async functions in textDocument/documentSymbols and textDocument/completion as well?
Contributor guide
No contributing guide indexed for this repository
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
Start by reading the protocol definitions for textDocument/semanticTokens, textDocument/documentSymbols, and textDocument/completion, focusing on how the existing async modifier is represented. Determine the protocol changes needed to expose async functions consistently and identify the relevant specification tests or examples. Done means the behavior is clearly specified across all three methods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100