Re: [lsp4e-dev] API Compatibility?

[Mickael Istria <mistria@xxxxxxxxxx>]

On Thu, May 18, 2017 at 5:34 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:

Greetings,

Hi,

I was brainstorming about a change I had in mind. Do we care enough at this point to not break existing clients or is it acceptable to have refactorings that will require downstream consumers to adapt their code?

LSP4E and all known clients are still incubating and I don't think anyone yet is committed to maintain stable APIs.
So it's still a good time for API changes. Note that if you can find ways to make change backward-compatible (by using default interface methods, or creating new interfaces/classes in the same hierarchy as the ones you want to change, or implementing auto-wrapping for extensions from old type to new type), that would be better though; but that wouldn't be a requirement.

People who want some backward compatibility could join the reviews and provide feedback/patches to enable backward-compatibility against your proposals.

HTH