Vitaly Slobodin
375bc88f95
Hello, this PR adds a new view to the LSP servers menu for displaying an LSP server capabilities. When I work on LSP stuff, quite often I need to check what capabilities an LSP server has. Currently there is no built-in way for checking that in Zed, and I have to use [`LSP DevTools`](https://lsp-devtools.readthedocs.io) project. LSP DevTools works OK but it works as a proxy between the client and the server, so setting it up is not that easy in Zed. Zed already has many goodies for LSP like tracing and RPC messages, so I thought that a simple view with server capabilities could be useful too. Thanks! ## Some screenshots: ### Ruby LSP  ### New menu entry:  Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.