-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discuss removal of some APIs #2466
Comments
There is also
How is this possible in a "non-breaking way"? I'm all for removing the default_clients (even if it would be breaking), but if someone used those configs, it would stop working for them, no? Or what am I missing? |
I can add code to migrate the "default_clients" to users LSP.sublime-settings "clients" section. (in reality, it would require more code, I would need to merge the "clients" configuration to "default_clients" and then move it to "clients", but you get the point) I would like to avoid people having to deal with breaking changes, unless they really have to... But that is just nice to have :) |
The easiest way to see if we are breaking a LSP-pacakge is by cloning
|
Some API are not necessary anymore.
While this removal might not happen soon,
I still wanted to give a heads up.
Client configuration
The following api will stay:
The following will be deprecated and removed:
Each package that still uses the deprecated api
will get an update to migrate to selector and priority_selector.
The text was updated successfully, but these errors were encountered: