This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-18
Channels
- # admin-announcements (3)
- # announcements (7)
- # aws (1)
- # beginners (76)
- # boot (340)
- # cider (9)
- # clara (35)
- # cljs-dev (7)
- # cljsjs (16)
- # cljsrn (11)
- # clojars (1)
- # clojure (192)
- # clojure-dev (6)
- # clojure-madison (8)
- # clojure-russia (373)
- # clojurebridge (1)
- # clojured (9)
- # clojurescript (172)
- # community-development (1)
- # core-async (2)
- # cursive (7)
- # data-science (2)
- # datomic (12)
- # devcards (1)
- # dirac (63)
- # emacs (3)
- # events (10)
- # gsoc (3)
- # hoplon (1)
- # jobs (1)
- # juxt (20)
- # ldnclj (4)
- # lein-figwheel (12)
- # leiningen (1)
- # off-topic (21)
- # om (232)
- # onyx (64)
- # parinfer (8)
- # proton (21)
- # re-frame (8)
- # reagent (1)
- # ring (3)
- # ring-swagger (3)
- # slack-help (4)
- # spacemacs (6)
- # testing (3)
Saves having to create channels for each juxt project
the problem is magically fixed when i do
(set! bidi/unmatch-pair
(fn [v m]
(when-let [r (bidi/unresolve-handler (second v) m)]
(str (bidi/unmatch-pattern (first v) m) r))))
@ul do you use handlers or keywords for targets? One guess is that equality on functions is broken in chrome's js somehow. I should think equality on keywords is more robust.
i use records as handlers, and equality for them works fine — I've debugged unresolve-handler
, comparison of given handler with handler in leaf gives true when they are meant to be equal
Can you strip things down to a small failing test-case?
I'm not sure how cljs works underneath, it still seems like magic to me