This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-15
Channels
- # babashka (4)
- # beginners (136)
- # calva (63)
- # clerk (7)
- # clj-kondo (8)
- # clojure (43)
- # clojure-boston (1)
- # clojure-europe (37)
- # clojure-nl (1)
- # clojure-norway (11)
- # clojure-uk (3)
- # clojurescript (6)
- # clr (1)
- # code-reviews (16)
- # cursive (45)
- # datomic (2)
- # docker (32)
- # emacs (10)
- # events (2)
- # exercism (1)
- # fulcro (3)
- # hugsql (1)
- # hyperfiddle (47)
- # leiningen (3)
- # lsp (30)
- # malli (39)
- # missionary (1)
- # off-topic (24)
- # pathom (2)
- # portal (14)
- # practicalli (5)
- # rdf (13)
- # reagent (18)
- # reitit (18)
- # releases (7)
- # remote-jobs (1)
- # sci (2)
- # shadow-cljs (45)
- # sql (7)
- # tools-build (11)
- # xtdb (13)
If I add (user/dev)
in a rich comment block clj-kondo complains with warning: Unresolved namespace user. Are you missing a require?
I think it's a common pattern and the user namespace should always be available from within a REPL (without the need for a require). Is this intentional/expected?
you can disable that linter in an RCF with:
:config-in-comment {:linters {:unresolved-namespace {:level :off}}}
So it's expected, thanks! I wasn't sure if I should create an issue about it on Github.
it's kind of an edge case. normally clj-kondo expects that you have a require
before you use a namespace
Makes sense 🙂
(I have a dev
ns with that sort of code in -- I avoid user.clj
to avoid auto-loading stuff -- and I use ((requiring-resolve 'dev/whatever))
in RCFs for reaching into that ns)