Should all server capabilities allow the corresponding dynamic registration options? about language-server-protocol HOT 2 OPEN

Is this just for backwards compatibility?

Yes, it is only for backwards compatibility. There could be old clients which don't support options. I tired to be consistent for all new requests I introduce.

The only solution that came to my mind when doing this was adding a client capability to inform the server. But it felt a little bit like overhead. If someone has an idea I am happy to look into this again.

from language-server-protocol.

Yes, I agree that you would probably need a capability (dynamicRegistrationDuringInitialize?). You can't just say the client can ignore the excess fields, since the server might prefer to dynamically register in order to make the settings have effect.

I agree it's some overhead, but it might be worth it. In particular, I don't know whether you have any plan to eventually mark some capability settings as deprecated, so as to push implementors towards the "recommended" way of doing things? If there's a path towards one day making the more sensible behaviour the default then it seems worth taking a step down that path.

from language-server-protocol.