Fork me on GitHub
#membrane
<
2023-01-04
>
zimablue16:01:13

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?

phronmophobic16:01:09

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.

zimablue16:01:28

you use self-hosted?

phronmophobic16:01:18

I use shadow-cljs

zimablue17:01:20

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?

zimablue17:01:40

Vars and introspection in cljs Vs clj make my brain bleed

zimablue17:01:56

*to Java objects

phronmophobic17:01:40

currently, the list of properties a component expects is also required

zimablue17:01:35

Which is what you helped me patch earlier in another thread with metadata, which is cool but read-time and a bit manual, got you

👍 2
zimablue16:01:25

but somehow the overall system still works?