This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-07
Channels
- # aleph (1)
- # announcements (2)
- # babashka (1)
- # beginners (49)
- # calva (1)
- # cider (5)
- # clj-kondo (14)
- # cljdoc (11)
- # cljsrn (6)
- # clojure (120)
- # clojure-austin (1)
- # clojure-europe (6)
- # clojure-finland (3)
- # clojure-italy (29)
- # clojure-nl (6)
- # clojure-spec (38)
- # clojure-uk (14)
- # clojurescript (65)
- # code-reviews (8)
- # cursive (20)
- # data-science (1)
- # datascript (5)
- # datomic (57)
- # emacs (6)
- # figwheel-main (2)
- # fulcro (32)
- # funcool (1)
- # jackdaw (7)
- # jobs (3)
- # joker (7)
- # kaocha (8)
- # keechma (3)
- # nrepl (7)
- # off-topic (25)
- # quil (3)
- # re-frame (10)
- # reagent (43)
- # remote-jobs (1)
- # ring (1)
- # shadow-cljs (173)
- # sim-testing (1)
- # spacemacs (1)
- # sql (3)
- # tools-deps (34)
Can I use clj-kondo's analysis info to obtain a dependency graph on the function level?
not yet. could be an interesting feature to add. if you can make a github issue for this with a compelling use case, that would be nice
I don't have any linters that use this information so I don't know how easy it will be to implement this
it's more of a curiosity at the moment, I often find myself tracing the execution of a function stack through many different parts of the file and across namespaces
It's easy to lose track of context doing that, and thought it would be nice to output a big Graphviz file where those dependencies could be seen visually
I imagine the following: each var-definition lists a :depends
list which has the vars it call. that's maybe not so hard to add and with this information you can build up this graph
btw @qythium, thanks for posting the other two bugs recently. those were fixed on master. I put the links to the new binaries in the issues.