This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (2)
- # babashka (52)
- # beginners (10)
- # calva (9)
- # cider (2)
- # clj-kondo (7)
- # clojure (63)
- # clojure-europe (26)
- # clojuredesign-podcast (5)
- # clojurescript (13)
- # datalog (2)
- # datomic (6)
- # defnpodcast (1)
- # fulcro (46)
- # incanter (4)
- # integrant (5)
- # jobs-discuss (12)
- # kaocha (1)
- # lsp (31)
- # malli (10)
- # meander (1)
- # off-topic (6)
- # podcasts (1)
- # polylith (20)
- # rewrite-clj (6)
- # shadow-cljs (23)
- # tools-deps (9)
- # xtdb (13)
- # yada (10)
Hi. I wonder what is allowed to put under an :alias. It looks to me putting :mvn/repos under an alias has no effect.
But the reference is vague on what I can do. https://clojure.org/reference/deps_and_cli
:mvn/repos is a top level key in deps.edn, along with
:aliases, so I wouldn't expect it to be used within one of the other top level keys.
I assume any other names than those of top level keys are usable within :aliases.
I use namespaced keywords to add context to the aliases and hopefully avoid clashing with any additional top level aliases that may be introduced in future (although things have been quite stable for a while)
Take :mvn/repos for example, no way I could know it cound’t be put into aliases, unless I put it and find there would be an error.
An extra question, do you know where to specify the .rebel-history file. Currently, it is always created under my working directory.
@i It makes sense that it would be created wherever you run a REPL using Rebel Readline — that’s exactly what nREPL does with its
I agree with Sean about the history as the large majority of expressions will be project specific. There is a global config file for rebel, but I don't see an option for setting a global history file. https://practicalli.github.io/clojure/clojure-tools/repl/customize-rebel.html If there really is a case for a global history file, then I suggest raising an issue on the rebel readline project.
The docs (for
deps.edn) are not as explicit as they could be.
deps.edn is described “with top-level keys
:aliases, plus provider-specific keys for configuring dependency sources” but you have to read the Procurers section much further on to find mention of the
:mvn/repos (top-level procurer-specific key). And I don’t see
:mvn/local-repo mentioned there (it’s another top-level procurer-specific key, to change the default
"~/.m2" folder path).