This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-11
Channels
- # aleph (7)
- # bangalore-clj (11)
- # boot (70)
- # cider (11)
- # cljsjs (3)
- # cljsrn (17)
- # clojure (88)
- # clojure-brasil (8)
- # clojure-dev (17)
- # clojure-greece (1)
- # clojure-italy (6)
- # clojure-poland (8)
- # clojure-russia (2)
- # clojure-spec (44)
- # clojure-uk (32)
- # clojurescript (176)
- # cloverage (2)
- # component (5)
- # cursive (3)
- # datomic (23)
- # defnpodcast (6)
- # dirac (15)
- # emacs (6)
- # garden (19)
- # hoplon (126)
- # leiningen (1)
- # off-topic (3)
- # om (66)
- # onyx (56)
- # re-frame (8)
- # reagent (7)
- # ring-swagger (43)
- # specter (18)
- # untangled (110)
- # vim (3)
- # yada (39)
@richiardiandrea any chance you could release https://github.com/boot-clj/boot-cljs-devtools/pull/5 to clojars soon please ? Would make it easy for our team to upgrade to Dirac 0.7.x
.
@superstructor sure, I don't know why, I missed that notification on Github, sorry about that!
@richiardiandrea I only pushed that minutes ago 😉
ah ah lol
will merge
tested locally and it works, havn’t looked into setting up figwheel-sidecar etc yet which would be an added change, but at least this gets it working like-for-like with previous Dirac releases.
@superstructor I have double checked boot-figwheel
and even though it looks what we need, it include piggieback
and therefore it does not "compose" with boot-cljs-devtools
, however a lot of code can be shared among the two...and I'll probably give it a spin in the next couple of weeks
ok cool thanks, for now above will get 0.7.x
working :thumbsup:
@superstructor 0.1.2
should be up
thank you! have verified the published jar as working with Dirac 0.7.1 🙂 @richiardiandrea
thank you for the quick patch
@darwin have you ever looked at filtering traces in the flame graph Timeline in devtools? Reason being, when performance profiling re-frame applications, there is a lot of stack frames that I don't care about, like all the internal CLJS stuff, and React. Being able to squash those frames down would be pretty incredible, cause you could just see the frames you wanted
@danielcompton no, I haven’t used timeline much
I think you should be able to use script blackboxing feature of devtools to get rid of noisy stackframes
I'll take a look, see if blackboxing is working today (it's been quite flaky in the Canary releases lately)