This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-11-15
Channels
- # announcements (1)
- # aws (79)
- # babashka (47)
- # beginners (82)
- # calva (65)
- # cider (27)
- # cljdoc (18)
- # cljs-dev (29)
- # clojure (189)
- # clojure-dev (5)
- # clojure-europe (3)
- # clojure-italy (1)
- # clojure-madison (6)
- # clojure-nl (4)
- # clojure-spec (10)
- # clojure-uk (41)
- # clojured (3)
- # clojurescript (5)
- # clojurex (17)
- # cursive (30)
- # data-science (7)
- # datomic (17)
- # emacs (3)
- # events (6)
- # fulcro (2)
- # funcool (9)
- # graalvm (29)
- # jobs-discuss (3)
- # joker (3)
- # kaocha (6)
- # malli (5)
- # music (6)
- # off-topic (21)
- # reagent (3)
- # reitit (4)
- # rewrite-clj (8)
- # shadow-cljs (49)
- # spacemacs (7)
- # sql (23)
- # tools-deps (15)
- # vim (43)
- # xtdb (19)
So assuming I was on your team for a second…
Presumably I’d need any personal aliases to be committed into that file? What about if I wanted to use classpath overrides etc, to stub a dep with a localised version etc? I like to use scope-capture, assuming noone did already would that need to be a conversation with the team, or would I just add it in as a dep into everyones :dev
alias?
I’m curious how the build script works… Does it start a repl as well as build stuff? Does it accept aliases as arguments? Or does it manages alias groups? i.e. ./build repl cider
would start it with cider ./build repl cursive
suitable for cursive etc?
What environments do people on your team use? Does everyone use chlorine and nrebl like you? Or do folk also user cider, intellij etc?
You have me thinking though, that there’s a benefit to the consistency wrt to transitive deps of always at least having things like the cider deps on the classpath even if not everyone uses it; it wouldn’t need to be loaded after all :thinking_face:
We optimise for pairing. And therefore value consistency very high.
We have Makefiles. And a make repl
creates an nRepl on a known port, and both Cider and Cursive is configured to connect to it. We also share configurations.
yeah they’re shaded by mr anderson — but not all tools/libs will do this.
if its always there yeah… if it’s something you can opt in to it doesn’t matter as much
I would say it's the other way round 😊 if it is bundled with the project and is always present then it doesn't matter. If I load it as a user, then it ought to be stable so I know I'm not causing the reproducibility problems that were mentioned.
You might be right but I was thinking more for stuff like: https://github.com/clojure-goes-fast/clj-async-profiler I tend to only include it one off when I need it; rather than always have it there… not sure what its deps are tbh.
As someone who likes to tinker and improve on my development process, I find the idea of not supporting personal aliases distasteful.
No one on our team uses CIDER or nREPL these days but there are still two aliases in our shared deps file for starting such things (old and new versions).
Yes, the build
script takes a list of aliases to use. Yes, it can start a REPL, REBL, Socket REPL, and several other variants (including old and new nREPL servers).