This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-30
Channels
- # arachne (1)
- # beginners (1)
- # boot (13)
- # cljs-dev (35)
- # cljsjs (12)
- # cljsrn (11)
- # clojure (77)
- # clojure-austin (14)
- # clojure-brasil (3)
- # clojure-france (1)
- # clojure-poland (4)
- # clojure-russia (23)
- # clojure-spec (39)
- # clojure-uk (14)
- # clojurescript (17)
- # cursive (16)
- # datascript (10)
- # devcards (1)
- # dirac (3)
- # editors (1)
- # emacs (4)
- # jobs (1)
- # jobs-rus (2)
- # luminus (5)
- # off-topic (1)
- # om (85)
- # parinfer (1)
- # perun (12)
- # re-frame (20)
- # reagent (4)
- # spacemacs (1)
- # specter (9)
- # yada (6)
@juhoteperi: i've been organizing issues in http://waffle.io, are you a fan of the kanban style thing?
@micha: Yeah, though haven't had much success with open-source projects
yeah i was trying to figure out a way to organize tickets that need more specification or discussion from actual work
@micha: Do we have issue about tasks being able to better control how exceptions are shown?
Maybe a few special exception metadata keys or even exception types which control what Boot does with the exception?
In boot-cljs and probably boot-alt-test I would like to handle pritting the exception from cljs compilation or tests myself BUT send exception to Boot so that the next tasks don't execute
@micha: ^ Created the issue. Feel free to tackle this if you have time, or I can do this in few days. Should be quite simple besides naming the exception type and option names 😄