This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-11
Channels
- # aws (2)
- # babashka (11)
- # beginners (107)
- # calva (6)
- # cljsrn (18)
- # clojure (180)
- # clojure-australia (6)
- # clojure-europe (54)
- # clojure-losangeles (9)
- # clojure-nl (4)
- # clojure-uk (13)
- # clojureladies (1)
- # clojurescript (57)
- # clojureverse-ops (1)
- # consultantsdirectory (1)
- # cursive (48)
- # datomic (11)
- # defnpodcast (3)
- # degree9 (1)
- # deps-new (5)
- # depstar (21)
- # docker (2)
- # fulcro (15)
- # helix (32)
- # kaocha (1)
- # lsp (21)
- # malli (15)
- # meander (15)
- # news-and-articles (2)
- # nextjournal (1)
- # off-topic (42)
- # pathom (3)
- # podcasts-discuss (1)
- # polylith (73)
- # protojure (1)
- # re-frame (43)
- # reagent (1)
- # releases (1)
- # restql (1)
- # schema (1)
- # sci (1)
- # shadow-cljs (23)
- # spacemacs (7)
- # sql (5)
- # tools-deps (42)
- # vim (15)
- # xtdb (3)
The new functionality with multiple files, should I be emphasizing folders of configs or something to make that work smoothly?
I suppose there's always limits with deps.edn, unless you're going to include tooling like antz has for updating the edn while preserving the whitespace?
Can you explain what you're asking? I don't understand the problem you're trying to solve.
I'm inventing hypothetical uses for the ability to add files to an existing project. I'm thinking about "Add the X library generation pack", which might add some deps aliases, stick a pom.xml in, maybe create some config files, that kind of thing.
Nah, I'm not tackling that problem. That sort of thing needs to be built on top of rewrite-clj(s) and I'm not going there.