This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-10
Channels
- # announcements (3)
- # asami (4)
- # babashka (21)
- # beginners (97)
- # calva (32)
- # cider (4)
- # clj-kondo (7)
- # cljdoc (1)
- # clojure (70)
- # clojure-europe (27)
- # clojure-nl (10)
- # clojure-norway (18)
- # clojure-uk (8)
- # clojure-ukraine (1)
- # clojurescript (5)
- # datalevin (7)
- # docker (1)
- # emacs (3)
- # fulcro (4)
- # girouette (4)
- # graalvm (2)
- # graphql (9)
- # gratitude (3)
- # honeysql (4)
- # hoplon (3)
- # hyperfiddle (7)
- # jobs (3)
- # kaocha (31)
- # lsp (23)
- # malli (7)
- # missionary (6)
- # nextjournal (9)
- # off-topic (6)
- # pathom (13)
- # polylith (13)
- # practicalli (3)
- # remote-jobs (3)
- # reveal (7)
- # schema (1)
- # sci (23)
- # shadow-cljs (31)
- # tools-deps (62)
- # xtdb (8)
@ericdallo heads up make
is broken on the cli
because of this line: https://github.com/ericdallo/deps-bin/blob/master/deps.edn#L3
due to the log4j vulnerability, I overrode to 2.17.2
and that seemed to work (you might have to rm
log4j from your .m2
dir to reproduce
I couldn't repro after removing log4j from .m2, but I released deps-bin 0.1.2 bumping most libs and bumped on clojure-lsp to avoid any issues
i would love a tool that allowed me to, in the source code on disk, move vars between namespaces, and have it automatically update all the relevant namespaces correctly - adding new requires, removing old (but only if they're not already correct). is there such a thing? how close are we to being able to do this? what's the next step?
It's a valid idea, and possible but not easy to implement it though, already mapped on this issue: https://github.com/clojure-lsp/clojure-lsp/issues/566
I can't recall, but doesn't clojure-lsp, when "new`ing" a new file (in vim, emacs?), have the ability to pre-populate the file form a template?
Ah okay. then I've spotted something then. I have a .projections.json
file which is used by vim-projectionist
that reads in a template (in effect, overwriting the (ns foo.bar)
. It works, but I've noticed that if the template has meta data in it, i.e: