This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-12
Channels
- # aws (21)
- # aws-lambda (8)
- # beginners (53)
- # boot (56)
- # braveandtrue (1)
- # cider (49)
- # cljs-dev (8)
- # cljsjs (1)
- # cljsrn (57)
- # clojure (403)
- # clojure-austin (17)
- # clojure-dusseldorf (10)
- # clojure-greece (9)
- # clojure-spec (57)
- # clojure-uk (144)
- # clojurescript (60)
- # datomic (149)
- # docker (1)
- # emacs (1)
- # hoplon (23)
- # humor (1)
- # jobs (1)
- # leiningen (2)
- # luminus (1)
- # off-topic (1)
- # om (24)
- # om-next (15)
- # onyx (23)
- # protorepl (2)
- # re-frame (58)
- # reagent (90)
- # remote-jobs (1)
- # ring-swagger (4)
- # slackpocalypse (1)
- # spacemacs (2)
- # specter (18)
- # untangled (4)
- # vim (1)
- # yada (27)
I’d like to setup an error handler in cljs.closure/watch
like we can with warning handlers
maybe I can setup a PR that inserts such an error handler here:
(catch Throwable e
(binding [*out* *err*]
(println (Throwables/getStackTraceAsString e))))
would allow users to customize error printing without implementing their own watch function, which seems fairly involved
trying to figure out the best way to change the api to allow this.
Thinking of adding build.api/*error-handler*
to keep the build.api/watch
api stable, and then pass the error-handler as an extra arg to closure/watch
@shaunlebron I don’t see why this can’t just be done as a new option