FWIW, for an API, I think it would be good to avoid having LSP4J classes in the API. So that we can replace the library that handles the communication if we need/want without breaking clients.
Also, I wonder why the server needs a command to start working - should not be that done automatically? (Does it really require all LSP clients to be modified to send it a command? Seems to be against the purpose of the protocol.) Anyway - having a way to run a (registered) command would sound great to me! Jan On Tue, Nov 24, 2020 at 2:46 PM Randamuna Namae <ioniv...@gmail.com> wrote: > Alright, will do. > > Thanks. > > On Tue, Nov 24, 2020 at 8:58 AM Jaroslav Tulach <jaroslav.tul...@gmail.com > > > wrote: > > > Dne úterý 24. listopadu 2020 1:15:19 CET, Randamuna Namae napsal(a): > > > Hello dear community, > > > > > > I'm working on integrating Apache NetBeans with Scala's LSP server and > > got > > > the basics working. > > > > That's great! Recently I needed to work with scala code (https:// > > renaissance.dev/ benchmark) and the old Scala support in NetBeans 8.x is > > no > > longer very reliable. > > > > > it seems that calling a command programmatically > > > wont be possible after all since the LSP classes are module private. > > > Is there a workaround for this? > > > > Prepare a PR that opens up the API slightly and let Jan Lahoda review it. > > -jt > > > > > > > > >
