This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-15
Channels
- # architecture (5)
- # babashka (34)
- # beginners (72)
- # calva (42)
- # cherry (31)
- # cider (14)
- # clojure (27)
- # clojure-europe (11)
- # clojure-norway (17)
- # clojure-uk (1)
- # clojurescript (25)
- # community-development (13)
- # conjure (1)
- # core-async (11)
- # datascript (18)
- # datomic (11)
- # emacs (12)
- # fulcro (10)
- # integrant (5)
- # introduce-yourself (3)
- # jobs (8)
- # juxt (2)
- # malli (22)
- # off-topic (11)
- # pathom (18)
- # polylith (62)
- # rdf (18)
- # reagent (8)
- # releases (1)
- # shadow-cljs (35)
- # sql (3)
- # squint (141)
- # tools-deps (12)
- # vim (4)
- # xtdb (4)
@nicola - at All Street we use visualise our Integrant dependencies graphs using Loom (requires graphviz). They end up as DAG SVG files. Nodes = Integrant components. Vertices = dependencies. The SVGs can be opened in a web browser and use the browser search to find labels.
You could do a similar graph of function names (nodes) and their dependencies (vertices). You may find it to be quite messy and hard to follow. Clojure can be read as EDN to produce this or there might be libraries already for this.
We found that at the function level, the code itself was a reasonable way to understand the relationships. Visualisations will take quite a lot of tweaking to make them look reasonable (e.g. blacklist common function calls from the graph like seq
, map
etc). The resulting graphs may also end up huge.
Thanks, I'm lookin for conceptual visualization rather implementation - aka block schema for algorithm, or ER for databases
Example screenshot from our codebase: