Re: [lsp4e-dev] workspace/executeCommand support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [lsp4e-dev] workspace/executeCommand support

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Mon, 30 Sep 2019 21:25:14 +0200
Delivered-to: lsp4e-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/lsp4e-dev>
List-help: <mailto:lsp4e-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/lsp4e-dev>, <mailto:lsp4e-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/lsp4e-dev>, <mailto:lsp4e-dev-request@eclipse.org?subject=unsubscribe>

> my lsp4e plugin along with other custom methods, what is the recommended approach?

My personal recommandation is to try to reject as much as possible customization on client-side. The value of LSP comes when there is no need for client-specific implementation; if you start needing it, then the features of your language server are not portable anymore and you get back to the N*M integration schemas LSP is meant to avoid.

Cheers

References:
- [lsp4e-dev] workspace/executeCommand support
  - From: Edmundo Lopez B.

Prev by Date: [lsp4e-dev] workspace/executeCommand support
Next by Date: Re: [lsp4e-dev] workspace/executeCommand support
Previous by thread: [lsp4e-dev] workspace/executeCommand support
Next by thread: Re: [lsp4e-dev] workspace/executeCommand support
Index(es):
- Date
- Thread

Breadcrumbs