Re: [lsp4e-dev] LanguageClientImpl not API?

[Mickael Istria <mistria@xxxxxxxxxx>]

Hi,

Because LSP4E is a relatively recent project, the default policy was to avoid as much API as possible to easily allow changes on the code and also reduce the maintenance effort (opening APIs have a long term cost on maintenance).

But LSP4E is now getting more mature, more stable, more used with a bigger and more active community of maintainers, so the project may now be able to provide more APIs like the one you're speaking about.

Please open an enhancement request for that with the technical details to support having it an API. Unless a technical limitation or a better solution appears, we'll then discuss best way of opening this as API (which package to export and so on).

Cheers.

--

Mickael Istria

Eclipse IDE developer, for Red Hat Developers