This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-01-04
Channels
- # announcements (8)
- # babashka (78)
- # beginners (15)
- # calva (6)
- # cider (12)
- # clerk (1)
- # clojure (46)
- # clojure-dev (13)
- # clojure-europe (15)
- # clojure-norway (5)
- # clojure-portugal (1)
- # clojure-uk (1)
- # clojurescript (23)
- # clr (29)
- # conjure (4)
- # core-async (10)
- # cryogen (1)
- # data-science (8)
- # hoplon (4)
- # hyperfiddle (11)
- # introduce-yourself (3)
- # jobs (6)
- # kaocha (12)
- # lsp (11)
- # malli (8)
- # membrane (11)
- # releases (1)
- # shadow-cljs (20)
- # spacemacs (47)
- # tools-deps (1)
in a vanilla (clj-compiler) cljs environment, there's no way to resolve vars right, so that part is expected to fail through to nil?
I haven’t tried the vanilla cljs compiler, but the defui macro also sticks the relevant info in an atom in case resolve isn’t available.
I use shadow-cljs
Sorry that's what I mean, I misspoke. I meant "normal" Vs "self-hosted", fwiw I believe shadow-cljs uses the "vanilla compiler" under the hood it just deals with peripheral elements of that process. Using shadow-cljs one can have resolve in the Java environment, to have objects, which is ok because the end goal is just to retrieve the ns right?
currently, the list of properties a component expects is also required