This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-31
Channels
- # announcements (22)
- # asami (19)
- # aws-lambda (4)
- # babashka (42)
- # beginners (43)
- # calva (28)
- # cider (1)
- # clerk (79)
- # clj-kondo (12)
- # clojure (47)
- # clojure-berlin (1)
- # clojure-brasil (1)
- # clojure-dev (12)
- # clojure-europe (40)
- # clojure-nl (2)
- # clojure-norway (5)
- # clojure-uk (3)
- # clojurescript (56)
- # clr (12)
- # conjure (8)
- # cursive (4)
- # datomic (78)
- # dev-tooling (6)
- # exercism (1)
- # fulcro (9)
- # hoplon (3)
- # jobs (3)
- # jobs-discuss (4)
- # lambdaisland (3)
- # leiningen (1)
- # london-clojurians (1)
- # lsp (125)
- # malli (32)
- # matcher-combinators (3)
- # nrepl (1)
- # off-topic (6)
- # pathom (39)
- # re-frame (13)
- # releases (2)
- # remote-jobs (3)
- # sci (7)
- # shadow-cljs (117)
- # sql (6)
- # squint (7)
- # tools-build (15)
- # tools-deps (12)
is there some way to share, say, a version or entry across multiple tools.deps entries? I am thinking of the git sha here: https://github.com/mentat-collective/Mafs.cljs/blob/main/deps.edn#L15-L18
This won’t work because we’re EDN not Clojure:
(let [sha "ec666210f11763fce4fec74072acca1e6525d29f"]
{:aliases
{:dev
{:extra-deps
{ {:git/sha sha}
{:git/sha sha}}}}})
This would work BACK IN THE DAY with Leiningen’s project.clj:
(def sha "ec666210f11763fce4fec74072acca1e6525d29f")
{:aliases
{:dev
{:extra-deps
{ {:git/sha ~sha}
{:git/sha ~sha}}}}}
Of course you can generate the deps.edn with a script (https://github.com/borkdude/rewrite-edn)
ah, nice