This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-26
Channels
- # announcements (7)
- # babashka (42)
- # beginners (349)
- # chlorine-clover (9)
- # cider (16)
- # circleci (2)
- # clj-kondo (6)
- # cljs-dev (61)
- # cljsrn (15)
- # clojure (95)
- # clojure-europe (11)
- # clojure-italy (2)
- # clojure-nl (4)
- # clojure-spec (4)
- # clojure-uk (24)
- # clojurescript (21)
- # conjure (2)
- # core-async (8)
- # cursive (12)
- # datascript (2)
- # emacs (4)
- # exercism (1)
- # figwheel-main (86)
- # fulcro (27)
- # graalvm (4)
- # helix (36)
- # hoplon (3)
- # interop (44)
- # kaocha (6)
- # lein-figwheel (4)
- # malli (7)
- # meander (9)
- # off-topic (95)
- # pathom (33)
- # pedestal (13)
- # re-frame (20)
- # reitit (3)
- # shadow-cljs (102)
- # tools-deps (14)
- # xtdb (16)
@seancorfield just published a new version that changed eval-and-render
to return a promise. This means that if you (let [res (editor/eval-and-render ...)] (prn res))
you'll see the result being printed. I believe this can help on commands that take too long to run.
eval-and-render
now also returns :result
(in case of success) or :error
(on failure). It can return nil
too, in case of some internal error, but I believe it'll happen only on some really edge-cases 🙂
Cool! Thank you!
What sort of thing will :error
be in that situation @mauricio.szabo?
For example, (/ 10 0)
- the exception will come inside :error
But, (try (/ 10 0) (catch Throwable t t))
will come inside :result
"the exception" -- just a message or an entire data structure?
Entire data structure. It's not "suitable for extension" yet, but it'll be soon~ish
(Something like that Browsable
that we were having trouble)
Just wanted to check before I put it in an Atom popup warning 🙂