Clojurians
#cljs-dev
<
2018-12-21
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

richiardiandrea00:12:49

is it a know problem that 1.10.439's stest/instrument does not contain ex-data anymore on failure?

dnolen01:12:49

I think so

dnolen01:12:56

look at the blocker tickets in JIRA

richiardiandrea01:12:24

uhm thank you folks, switching to orchestra for now, waiting for having more time for debugging

richiardiandrea02:12:16

It might be related to expound, it rings a bell and I am afraid there was some incompatibility with 1.10.439

borkdude10:12:00

what’s the issue with stest/instrument not containing an ex-data on failure? can’t find it in JIRA

richiardiandrea16:12:56

I haven't found it as well, but Mike's example seems to show different things. In my case I tried to js/console.dir the ex-info sent down a code path and I did not see any data...but I will need to debug that more

fdserr10:12:17

Hi there. Small paradox: doc at https://clojurescript.org/reference/repl#auto-loaded-user-code says we can have a user ns, but the compiler (as 1.10.338) doesn't agree: WARNING: user is a single segment namespace at line 1.... Did I miss an episode? Is this worth a ticket?

mfikes12:12:43

@fdserr The doc doesn’t actually say you can have a user ns. The namespace in that file can be whatever you like. The default, if unspecified is cljs.user.

fdserr12:12:03

Hi Mike. Let me please try to rephrase? I can have a user.cljs file (prolly in /dev folder), with a (ns cljs.user) decl inside, and its Vars will be picked-up at REPL startup. Correct?

mfikes12:12:12

Yes, and in that case the Vars will indeed be available in the REPL.

fdserr12:12:15

Awesome! thanks much.

mfikes12:12:54

@fdserr FWIW you can omit (ns cljs.user); it is optional.

fdserr12:12:56

Got it, just the file has to be named user.cljs right?

mfikes12:12:55

That, or user.cljc

mfikes12:12:41

If you see any improvements to the doc, feel free to contribute. If you read it you will find that it is consistent with the above, but perhaps it isn’t as clear as it could be.

fdserr13:12:29

Well, the time has gone when one could just propose edits on github pages :smiley: do you think it's worth a ticket?

mfikes13:12:52

But, to answer your question: The docs are clear to me. But that doesn’t mean they are clear.

fdserr13:12:44

Lol, you pretty much invent this stuff, hopefully crystal clear for you ^ Let me re-read and consider this... Thanks a bunch for the heads up!

fdserr13:12:47

@mfikes Done. Greetings :spock-hand: