According to https://www.clojurescript.org/about/differences, cljs.spec and cljs.test are ports of their respective clojure namespaces.

But I’ve got some cljs tests that require the clojure namspaces (not the cljs namespaces) and everything seems to run just fine.

Is there a reason to prefer requiring cljs.spec and cljs.test in cljs tests or does it not really matter?

IMO it doesn’t really matter and I slightly prefer using clojure.*

but someone might disagree with me

since so many libs relied on clojure.core clojure.test etc., they implemented special handling of it in the compiler to rewrite clojure.* to cljs.*

When using Cljsbuild with whitespace optimization this worked fine (.-addr (.-dataset e) where addr is a custom attribute. Then when setting optimization to advanced, I am getting nil. Any idea whats going on?

For some odd reason I had to do (aget target-el "dataset" "addr")

you should avoid property based access for data

goog.object/get is preferred, avoid aget - only for arrays

you need a faq page to just point to that @dnolen :) (like https://clojure.org/guides/faq)

yeah 🙂

@mario.cordova.862 under advanced compilation property access will get renamed - that's why it doesn't work and should be avoided - (unless it's JS language properties or mature standard browser APIs)

@david_clojurians we auto-alias clojure.foo -> cljs.foo - it helps with portability (i.e. cljc files) - it's intentional so feel free to use that feature as you see fit

@posobin you can trivially await promises w/ core.async - there's a patch to add support to core.async directly that I need to review once more

is there a way to preprocess some files before compilation like converting svgs to hiccup components?

Has anyone had any luck getting a react async select to work in cljs? the callback/promise on loadOptions is throwin me off

I suppose the root of the issue is- anyone have any tips for interop that requires a promise / callback? Do I use a go block?

Callbacks and promises work in CLJS the same as JS

Why can’t you use promise?

Perhaps I'm confused at a lower level of understanding. I'll look into using a promise directly

@shanelester55 Here's a script which uses promises directly: https://gist.github.com/yogthos/d9d2324016f62d151c9843bdac3c0f23#file-gallery-cljs. Maybe the example is useful to you.

Ahh thank you!

Boy, this is perplexing. I got an error f.call is not a function, stack trace indicates that it was happening in clj->js. Ok, I’ve got some values that I’m passing to clj->js, I’ll pprint them and see what the problem is. Now I’ve got f.call is not a function in pprint. Ok, printing doesn’t work, I wonder what the types are for those values? So I try (doseq [v values] (pprint {:type (type v)})). Now I’ve got f.call is not a function in Object.cljs$core$accumulating_seq_count.

What the heck have I got in my data that’s making everything blow up like that??

(Apparently that last one may be happening in a call to seq or count. Or both.)

@manutter51 do you have a lazy seq in that data? that'll make things look weird sometimes

Ah, yes, I do, thanks for the clue, that wouldn’t have occurred to me

Oh word, I accidentally had the arguments to remove in the wrong order. What a wild way for that bug to show up!

Tks much @thheller I’d have been all afternoon on this one. 😉

I'm looking for a good reference for how to evaluate CJLS expressions in the browser. Goal being allowing users to define functions (like defining a formula in an excel spreadsheet).

I found this article dated 2015. Is it a good approach or have things moved on? https://yogthos.net/posts/2015-11-12-ClojureScript-Eval.html