This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-19
Channels
- # announcements (9)
- # babashka (5)
- # babashka-sci-dev (23)
- # beginners (160)
- # calva (78)
- # cider (23)
- # clj-commons (2)
- # clj-kondo (5)
- # cljdoc (19)
- # cljs-dev (8)
- # clojure (54)
- # clojure-australia (1)
- # clojure-czech (2)
- # clojure-dev (17)
- # clojure-europe (8)
- # clojure-italy (8)
- # clojure-nl (2)
- # clojure-sg (3)
- # clojure-uk (4)
- # clojurescript (70)
- # community-development (8)
- # core-async (8)
- # cursive (7)
- # datahike (12)
- # datalog (22)
- # datomic (20)
- # events (1)
- # fulcro (43)
- # graalvm (92)
- # gratitude (5)
- # holy-lambda (77)
- # honeysql (1)
- # jobs (1)
- # lsp (111)
- # membrane (70)
- # nextjournal (13)
- # off-topic (73)
- # pathom (1)
- # polylith (8)
- # portal (32)
- # re-frame (3)
- # reagent (4)
- # reitit (5)
- # releases (2)
- # reveal (4)
- # xtdb (22)
So this is what you get when linting JVM Clojure (see screenshot). When I would remove the magic for goog.array/goog.object then the error message would become the same for CLJS.
You can disable this with {:linters {:unresolved-namespace {:exclude [goog.object]}}}
already. So this would probably be sufficient, unless it's preferred to have a bespoke message around CLJS deprecating this.
I can make a new clj-kondo release with the goog.array / goog.object magic removed when CLJS will be released (on or around the same day).
Just making sure: should any namespace except goog
or goog.base
follow that rule from now on?
The rule doesn’t extend to ClojureScript in general - i.e. it is of course useful in the writing of macros