Skip to content
This repository has been archived by the owner on Mar 6, 2022. It is now read-only.

How to restrict the server capabilities by the client? #56

Open
przepompownia opened this issue Jan 21, 2022 · 2 comments · May be fixed by #58
Open

How to restrict the server capabilities by the client? #56

przepompownia opened this issue Jan 21, 2022 · 2 comments · May be fixed by #58

Comments

@przepompownia
Copy link
Contributor

I spent some hours to find how to launch the server with the restricted set of capabilities. Excluding some of them on the nvim built-in client side (e.g. capabilities.textDocument.definition = nil) on initialization gave no effect for me.

I guess (I hope I'm wrong) it's currently not possible. Does then each extension need to be prevented from registering particular handler depending on the client's capabilities?

@dantleech
Copy link
Contributor

Yeah, not currently possible to adapt to the client s requirements/restrictions.

Open to ideas, maybe a "isSupported(Client capabilities $capabilities)" on the handler itself?

@przepompownia
Copy link
Contributor Author

przepompownia commented Jan 22, 2022

Please look on the example approach in #58

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants