This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-02-05
Channels
- # announcements (1)
- # asami (25)
- # babashka (78)
- # beginners (24)
- # clojure (15)
- # clojure-europe (21)
- # clojure-losangeles (4)
- # clojure-nl (1)
- # clojure-norway (13)
- # clojure-uk (11)
- # cursive (17)
- # datomic (29)
- # events (1)
- # fulcro (4)
- # hyperfiddle (6)
- # jobs (1)
- # lsp (20)
- # malli (9)
- # off-topic (7)
- # pedestal (1)
- # polylith (2)
- # practicalli (1)
- # rdf (7)
- # reitit (1)
- # remote-jobs (1)
- # spacemacs (17)
- # specter (24)
- # vim (1)
little documentation update for the call hierarchy tutorial section: https://github.com/emacs-lsp/lsp-mode/pull/4324
I have implemented the Project Tree view in coc-clojure (release forthcoming), and I have some thoughts on its design. What’s the best method of relating those to y’all?
what do you mean "print"?
oh sure!
the two thoughts i have are: 1) can there be a :node-type on the returned nodes? typescript doesn't handle open maps as well as clojure, so having a more obvious method of "this is a branch, that is a leaf" would be helpful. 2) is it possible to send the whole tree at once? on a small project, it's not so bad to open each item one by one, but on a big one, it feels onerous to have to click through everything.
1. I'd like to avoid that as there are other LSP methods/responses that you can infer the type only with the given fields, but if that's critical to make the feature work on nvim, I think we could add 2. I'd like to avoid that as well 😅, that's something the client should support, for example on emacs treemacs there is a option to treemacs open each child until no more child exists and that works great for some features. Since this is a feature that can load lots of info, it's good to be lazy like call hierarchy
A "node type" isn't necessary, it would just be helpful/useful. Otherwise, I have to be slightly more verbose in my checking (to help the type checker).
and makes sense about the lazy perspective. i'll experiment with a setting to allow for calling recursively, see how slow that is. (thankfully, clojure-lsp is returning results in sub 1ms on my 2018 laptop, so i don't think that'll be the issue here)
yeah, the problem is more related with the json traffic, clojure-lsp is indeed very fast after startup 💅 , but communicating via JSON LSP logs all the ns, functions, java classes and jars of a project, can take a lot for medium/big projects
yeah it's very cool! the coc.nvim docs aren't great, but now that I understand how it works, I hope to get this working for the test tree and for the call heirarchy as well.
Am I doing something wrong? I try to rename a ns using , r r on the ns name, want to move it from core/db.clj to lib/db.clj but when I run the command and rename it to lib.db it kills all the aliased requires. I.e. if something was [core.db :as db] it becomes [lib.db (doesn't retain the alias nor the syntax)