-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
Use new custom LSP method for server info command and print info in "Calva says" output channel #1211
Labels
Comments
23 tasks
@PEZ, regarding the above, where should we show this information to the user now? Some ideas:
|
I like the third option :) |
bpringe
changed the title
Use new clojure-lsp server info command
Use new clojure-lsp server info command and print info in Calva says output channel
Jul 11, 2021
bpringe
changed the title
Use new clojure-lsp server info command and print info in Calva says output channel
Clojure-lsp Server Info command: use new custom lsp method and print info in Calva says output channel
Jul 11, 2021
bpringe
changed the title
Clojure-lsp Server Info command: use new custom lsp method and print info in Calva says output channel
Clojure-lsp Server Info command: use new custom LSP method and print info in Calva says output channel
Jul 11, 2021
bpringe
changed the title
Clojure-lsp Server Info command: use new custom LSP method and print info in Calva says output channel
Use new custom LSP method for server info command and print info in "Calva says" output channel
Jul 12, 2021
23 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The clojure-lsp command used currently by Calva is being deprecated in favor of a new custom command that will return the server info and include additional information.
We should make the implementation for Calva's clojure-lsp server info command use the new custom command instead of the now deprecated one.
Reference: clojure-lsp/clojure-lsp#450 (comment)
The text was updated successfully, but these errors were encountered: