microsoft / microsoft/language-server-protocol
Protocol extension to drive UI components
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
👋 Have there been any attempts to provide an extension to the protocol to standardise UI contribution for LSP-based extension developers?
If not, is this planned or would it be possible to standardise it, should such an attempt be made?
Context
The benefit of language server is that it's code editor/IDE independent. UI components are normally editor-specific, however there are certain presentational layer elements that are shared by many code editors. For instance, tree view components can often be implemented by different vendors (e.g. editors often have "File Outline" as tree view).
As an extension developer, it's hard to maintain such UIs per each IDE that are enabled via LSP. Another example of such is web view UI component, which allows extension developers to create fully customisable views.
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
The issue does not name any files, tests, or entry points. Start by reviewing the existing LSP protocol capabilities and the editor-specific UI examples described in the issue; done would require a clearly scoped, agreed proposal for standardizing shared UI contributions.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100