Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lsp_log: Add server capabilities view #19448

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

vitallium
Copy link
Contributor

@vitallium vitallium commented Oct 19, 2024

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 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

CleanShot 2024-10-19 at 07 44 38@2x

New menu entry:

CleanShot 2024-10-19 at 07 45 08@2x

Release Notes:

  • N/A

Adds a new view to the LSP servers menu for
displaying an LSP server capabilities.
@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label Oct 19, 2024
Copy link
Contributor

@osiewicz osiewicz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, though I'm curious on @danilo-leal or @iamnbutler opinion on the # of entries for a single language server in that list. It's getting a bit packed and I wonder if two-level list would be a better solution instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed The user has signed the Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants