microsoft / microsoft/language-server-protocol
Add new CompletionItemTag "static"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
It's useful for a user to know whether a candidate function is static or not, so there should be a corresponding tag.
Motivating C++ example:
struct S {
void func1();
static void func2()
};
S::fu/*complete here*/
Only func2 is valid for calling here, but the server will likely not be able to just omit func1, as the user might want to take a pointer to it, which is allowed. It will help the user immensely if the (non-)static-ness of the candidates is exposed here.
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 CompletionItemTag definition and the surrounding language server protocol specification. Check how a static completion tag would be represented and documented; done means clients can distinguish static candidates from non-static ones without losing support for taking pointers to non-static functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100