This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-02
Channels
- # admin-announcements (3)
- # architecture (5)
- # beginners (10)
- # boot (223)
- # cider (13)
- # cljsjs (2)
- # cljsrn (50)
- # clojure (208)
- # clojure-austin (16)
- # clojure-belgium (1)
- # clojure-india (1)
- # clojure-poland (13)
- # clojure-russia (130)
- # clojure-spec (27)
- # clojure-uk (144)
- # clojurescript (135)
- # css (2)
- # cursive (10)
- # datavis (1)
- # datomic (29)
- # dirac (9)
- # funcool (2)
- # hoplon (41)
- # jobs (3)
- # leiningen (6)
- # om (37)
- # onyx (20)
- # pedestal (1)
- # planck (1)
- # proton (4)
- # re-frame (45)
- # reagent (17)
- # rethinkdb (16)
- # ring-swagger (19)
- # schema (5)
- # specter (93)
- # sql (16)
- # test-check (33)
- # untangled (7)
@darwin: would you take a PR to remove the log4j dependency in dirac?
To replace it with clojure.tools.logging?
We’re using logback, and we get a red warning when we run a REPL
I’ve moved the dirac dep to a separate profile that is only used for CLJS and that seems to be working well
I’m pretty sure Cursive will work for stuff put in common profiles, like :dev
if they’re all just for dev/test then they should be fine in the :dev
profile
@danielcompton: I’m open to any improvements. Just cannot comment directly on log4j you raised, because I don’t understand java-side that much.
just finished v0.8 of cljs-devtools and with :async feature and Dirac 0.6.3 you can have long stack traces when pausing in core.async code https://github.com/binaryage/cljs-devtools/releases/tag/v0.8.0