| Hi Jonah,
LSP is designed for the type system of TypeScript, and so it happens quite often that they introduce a change that is non-breaking for TypeScript, but breaking for Java. In LSP4J we chose to accept those breaking changes in order to stay as close to the original protocol as possible. But it’s important to announce the changes in the CHANGELOG.md.
Cheers Miro
Hello fellow lsp4j-devers,
In a recent change to DAP some of the fields which used to be generic numbers have been changed to be specified as integers with a range of 0 to 2^31-1. In the past we represented those numbers as java Long in LSP4J's implementation, but now we could use java Integer.
Making this change would make it a breaking change Java API-wise.
Has LSP4J for language server side of things dealt with this before? What is the process for changing the Java API in LSP4J?
Thanks for your input. Jonah
_______________________________________________ lsp4j-dev mailing list lsp4j-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/lsp4j-dev
-- Dr. Miro Spönemann
Software engineer and consultant
Am Germaniahafen 1, 24143 Kiel
Tel.: +49 151 42679459
Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 Geschäftsführer: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein
|
