This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-16
Channels
- # beginners (103)
- # boot (48)
- # cider (2)
- # clara (12)
- # cljsrn (9)
- # clojure (133)
- # clojure-art (3)
- # clojure-dev (9)
- # clojure-korea (7)
- # clojure-russia (228)
- # clojure-spec (8)
- # clojure-uk (26)
- # clojurescript (131)
- # cursive (8)
- # datomic (30)
- # emacs (4)
- # events (2)
- # hoplon (47)
- # lein-figwheel (5)
- # off-topic (1)
- # om (12)
- # onyx (337)
- # perun (23)
- # planck (15)
- # proton (3)
- # re-frame (5)
- # spacemacs (20)
- # untangled (97)
- # utah-clojurians (1)
- # yada (13)
do you think my PR might get love or not today? Appreciate I went for the PR->convo route, rather than the convo->PR route with it, and everyone's busy, would like to avoid having to push a 'special' version to somewhere is all.
Is there any danger in returning stack traces on for example a 403?
Are there specific bad things that can happen, and if so can I hide/disable it in yada?
ah - found a page in the manual to turn them off!
sure: https://juxt.pro/yada/manual/index.html and then ctrl+f for “stack trace"
I’m borrowing that set/range
combo...