This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-02-23
Channels
- # announcements (1)
- # babashka (68)
- # babashka-sci-dev (12)
- # beginners (36)
- # biff (22)
- # calva (20)
- # clerk (1)
- # clj-on-windows (7)
- # clojure (27)
- # clojure-conj (8)
- # clojure-denmark (2)
- # clojure-europe (141)
- # clojure-france (1)
- # clojure-italy (4)
- # clojure-nl (1)
- # clojure-uk (2)
- # clojurescript (7)
- # conjure (8)
- # core-async (111)
- # cursive (3)
- # datahike (4)
- # datalevin (18)
- # events (9)
- # gratitude (4)
- # guix (2)
- # helix (3)
- # hyperfiddle (62)
- # introduce-yourself (2)
- # kaocha (4)
- # london-clojurians (3)
- # lsp (7)
- # malli (34)
- # membrane (1)
- # nbb (9)
- # polylith (4)
- # portal (6)
- # reagent (4)
- # releases (2)
- # remote-jobs (4)
- # shadow-cljs (30)
- # sql (2)
- # tools-deps (58)
- # xtdb (9)
Is there a way to configure Calva to parse links/references in docstrings the https://docs.cider.mx/cider/usage/working_with_documentation.html#generating-documentation-cross-references?
Not currently, but it’s probably possible to implement in Calva. Feel free to create an issue for it.
that's something it's expected to work in a LSP hover request, but the spec only mentions support for markdown and that's why [[my-link]]
is not recognized, you can see changing to [my-link](real-link)
works
if we really want to support this custom format like cider, would need to make changes for every client, like calva, lsp-mode, vim etc and some of them are generic enough to not be easy to support that, so maybe as last resource, clojure-lsp could convert [[my-link]]
to [my-link](my-link)
and that would probably make work for everyone
is that format that common/important @U0ENYLGTA?
It would be if it worked across clients 🙂
It's super helpful because you get active links directly to other functions (if you're in an editor) or other docs (if you're reading codox-generated docs).
I wouldn't call this urgent! But I think it'd be useful.
I think we can do a simple replace on clojure-lsp side to support that on all clients, makes sense, would you mind open an issue on clojure-lsp?
Actually, would that even work? Codox transforms [[<symbol>]]
into a link to the doc for that symbol. I don't think converting that to [<symbol>](<symbol>)
would result in a usable link.
oh, didn't know about that, so it's more complex, I'm not familiar with codox, not sure how it works
it seems it kind of find the element between quotes and build something like [<symbol>](<the-result-of-finding-symbol>)
right?
hum, we could make clojure-lsp find the definition of symbol
and build that url, but would need a little bit more testing if that is enough
but it's something that is interesting for all docs that use quotes indeed, which is pretty common
I hadn't thought of that! Imagine clicking through from "some doc that references another-function
! One problem would be how to select the function in the face of unqualified symbols, or, worse, qualified symbols that use random aliases.