This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-06-06
Channels
- # babashka (40)
- # beginners (14)
- # calva (3)
- # cider (7)
- # clerk (40)
- # clj-kondo (8)
- # cljfx (3)
- # clojure (79)
- # clojure-berlin (1)
- # clojure-denver (14)
- # clojure-europe (30)
- # clojure-nl (6)
- # clojure-norway (21)
- # clojure-uk (4)
- # clojurescript (10)
- # conjure (4)
- # data-science (13)
- # emacs (21)
- # events (8)
- # hoplon (7)
- # hyperfiddle (25)
- # lsp (11)
- # matrix (1)
- # off-topic (110)
- # pathom (11)
- # pedestal (7)
- # reagent (13)
- # reitit (16)
- # ring (10)
- # shadow-cljs (6)
- # timbre (3)
- # vim (8)
- # wasm (3)
How is clj-kondo supposed to work with the pre-defined babashka-aliases? (https://book.babashka.org/#built-in-namespaces)
I've gotten used to explicitly requiring everything, including the already-aliased things like json
, str
and pprint
, partly because I like having requirements be obvious, but mostly because I don't like seeing the squiggly-line telling me that I'm referencing an unresolved namespace.
Is the current design of clj-kondo meant to react on the built-in babashka aliases, or do I have some weirdness in my setup?
Don't rely on the pre-defined aliases outside of one-liners on the command line. When you are making a script, just use require
etc with your own aliases