Skip to content

Surface errors when developing ruby-lsp or ruby-lsp-rails #1585

@vinistock

Description

@vinistock

Depends on Shopify/vscode-ruby-lsp#571

When errors occur in the server, we send them to telemetry if a client is defined by a private extension using the ruby-lsp.getPrivateTelemetryApi command.

However, when we're working on the ruby-lsp or ruby-lsp-rails themselves, we should shorten this feedback loop and just display the errors directly in the window.

Let's start checking if we're working on these two projects and then, instead of sending telemetry on errors, we just use vscode.window.showErrorMessage to pop up the error to immediately bring it to our attention.

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions