microsoft / microsoft/language-server-protocol

Review/give feedback on the build server protocol (BSP)

Open
#512 7 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion
Dominant language
TypeScript
Stars
13k
Forks
1k
Avg merge
6d 1h
Merged PRs (30d)
10

Description

Announcement of the Build Server Protocol (BSP) is here.

As explained in https://github.com/Microsoft/vscode/issues/52462, the BSP team at the Scala Center and JetBrains is interested in listening to feedback on the protocol. The protocol closely follows LSP's design. I think we could gain a lot of interesting insights from the maintainers of this repository.

(The major difference is the way we handle file watching endpoints; we use static capabilities + specific file watching endpoints instead of dynamic capabilities -- we think this design is simpler and easier to implement in both clients and servers, but it's less relevant in the grand scheme of things.)

I'm currently working on an official website built on Docusaurus to aggregate all relevant information relevant to the specification and the motivation. In the meanwhile, I encourage you to read the following links to grasp which problem we're solving and how we're solving it:

  1. The specification of BSP
  2. Which MxN problem is solved
  3. What role IDEs and non-IDEs (editors) play

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the linked BSP specification and the related discussions on the MxN problem and IDE/editor roles. Compare BSP's design with LSP, paying particular attention to static capabilities and file-watching endpoints. Done means providing actionable feedback to the BSP team; no repository file or test is identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.