Fork me on GitHub
#chestnut
<
2017-09-07
>
vinai13:09:58

Hm, actually, component on the frontend only starting the "UI" component (which isn't even a real component) is a bit of a nuisance because it swallows exceptions thrown by UI components. I haven't figured out yet how to see the actual error stacktrace, It's just "Error in component"...

vinai13:09:24

Taking component out is quite a bit harder then taking out the system library on the backend.

vinai13:09:34

But I'll try.

vinai13:09:39

Grr, failure for now.

vinai13:09:52

Running out of time.

featheredtoast17:09:03

sorry for the troubles - Component was added to the frontend so it'd be easier to reload stateful services (bidi, websockets, event handlers, etc).

featheredtoast17:09:09

You can catch and print your stacktraces inside your component though.

(try (render)
         (catch js/Error e (println (.-stack e))))

featheredtoast17:09:23

that shouldn't be necessary though as the original stack trace is available in the observed exception's "cause" anyway