Fork me on GitHub
#clojurescript
<
2019-11-16
>
dnolen00:11:47

@mhuebert fwiw, I don't see a problem w/ storing that info

4
Saikyun09:11:00

when running cljs in the browser, whenever I get instrumentation errors, they look like this: https://memset.se/10285/2b7a49f7a07ea1a07a2f3ed159b9728945da2fc1

erwinrooijakkers16:11:24

Maybe catch the exception and beautify for example with expound? https://github.com/bhb/expound

erwinrooijakkers16:11:43

Ah I see this answer is on old question

erwinrooijakkers16:11:14

Maybe you already had an answer, but expound is great for making human readable messages 🙂

bbrinck21:11:35

Here is some code for catching the exception and formatting with expound https://github.com/bhb/expound/issues/152

Saikyun07:12:28

@U2PGHFU5U @U08EKSQMS I actually ended up using expond 🙂 thanks for the tip.

👍 8
Saikyun09:11:16

is there a way to get more descriptive errors? I can't even figure out what call caused this to happen

Saikyun10:11:27

essentially I'd want to see the message part of the error printed into the console

Saikyun10:11:40

is there a way to modify how spec deals with the errors?

p-himik10:11:28

I don't think there's a way to modify it. But The "Uncaught" message has data field in it that you can expand that should contain all that you need.

Saikyun15:11:14

thanks for the tip. sadly, I can't find information about what called the function there

p-himik15:11:44

The triangle in the top left corner should expand the full stack trace.

Saikyun15:11:54

under data it looks like this, i.e. only calls to spec (and the function that crashes): https://memset.se/10286/025a2f93c1c98f642588b9f6904b25c868f2c8f9

Saikyun15:11:27

further down there's a stack-property, but I can't look at it, because if I click it it says "too long to edit": https://memset.se/10287/f4c54d240885c0a7a079ff18782b99d339a4e979

p-himik15:11:08

The top left triangle.

p-himik15:11:22

Right to the left of Uncaught (in promise).

Saikyun15:11:53

ah neat, thanks. 🙂

p-himik15:11:09

No problem.

Saikyun15:11:31

and thanks for the link, will try it!

Saikyun15:11:44

I'm pretty new to cljs development, so very thankful for this kind of info! 😄

fossifoo14:11:25

i try to put! the content of a col into a core.async pipeline and want them to be received in order. what's the sane way to do this?

alexmiller14:11:07

pipeline retains order

fossifoo14:11:37

so it will keep the order that i called put! in? i thought i had a race condition due to this

fossifoo14:11:17

ah, wait. i now realise that my issue is actually a different one

fossifoo14:11:35

i need to know when the last value has been put. and that should be easy

fossifoo14:11:48

yeah, works. thanks

Aleks Abla19:11:59

hey everyone, having a little bit of trouble understanding this piece of code. what is the purpose of using and in this let statement, and why would we choose to do this?

andy.fingerhut19:11:03

Likely the intended usage of the function facet-row is that either selected-facets is nil, in which case it should not be called as a function, or it is a function, and it should be called. The and expression prevents the function call if selected-facets is nil. It could be written equivalently as (if selected-facets (selected-facets (first facet)))

Aleks Abla19:11:30

awesome, thanks for clarifying!