microsoft / microsoft/language-server-protocol
Support for these complex snippets should be a capability
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Also, support for these complex snippets should be a capability. It seems that as soon as you declare support for snippets, you're binding yourself to implementing a potentially changing snippet specification.
Or at least, version the specification of snippets maybe ?
For example, in Vim there's no way to support JavaScript regexes without writing a JavaScript to Vim regex compiler
See https://github.com/microsoft/language-server-protocol/issues/363
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 linked Language Server Protocol issue 363 and the current snippet-support specification. No files, tests, or implementation entry points are identified in this issue. Done would require an agreed protocol design for representing snippet capabilities or versioning the specification, rather than a narrowly scoped code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vim
- 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