One breaking change, that they doesn't list as breaking (I guess since I assume the old was always broken) is:
Dynamic registration of LSP capabilities. An implication of this change is that checking a client's server_capabilities is no longer a sufficient indicator to see if a server supports a feature. Instead use client.supports_method(). It considers both the dynamic capabilities and static server_capabilities.
So if you had code like
if client.server_capabilities.inlayHintProvider then
...
end
you now should use
if client.supports_method("inlayHintProvider") then
...
end
So, not really a breaking change I guess, but something you should change any way.
6 Comments
ericjmorey@programming.dev · 3 pts · 2y
Lots of breaking changes. It seems like all of the changes are breaking something according to these release notes.
autokludge@programming.dev · 13 pts · 2y
Also my CPU now longer overheats when holding space. WTF?
80avin@programming.dev · 3 pts · 2y
Isn't that a feature?
snaggen@programming.dev · 2 pts · 2y
One breaking change, that they doesn't list as breaking (I guess since I assume the old was always broken) is: Dynamic registration of LSP capabilities. An implication of this change is that checking a client's server_capabilities is no longer a sufficient indicator to see if a server supports a feature. Instead use client.supports_method(). It considers both the dynamic capabilities and static server_capabilities.
So if you had code like
you now should use
So, not really a breaking change I guess, but something you should change any way.
sxwpb@lemmy.world · 3 pts · 2y
new disable foldtext option is cool
hedy@lemmy.sdf.org · 3 pts · 2y
Finally! Something similar to
M-x eval-regionbuilt-in (as far as I'm aware).