This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-27
Channels
- # bangalore-clj (2)
- # beginners (41)
- # cider (14)
- # cljs-dev (12)
- # cljsrn (2)
- # clojure (106)
- # clojure-austin (6)
- # clojure-dev (22)
- # clojure-dusseldorf (1)
- # clojure-france (1)
- # clojure-greece (17)
- # clojure-italy (6)
- # clojure-poland (3)
- # clojure-russia (10)
- # clojure-serbia (5)
- # clojure-spec (24)
- # clojure-uk (100)
- # clojurescript (126)
- # cursive (3)
- # data-science (5)
- # datascript (15)
- # datomic (3)
- # defnpodcast (2)
- # dirac (6)
- # emacs (10)
- # fulcro (121)
- # graphql (30)
- # hoplon (7)
- # jobs (2)
- # leiningen (20)
- # off-topic (14)
- # onyx (3)
- # other-languages (13)
- # pedestal (1)
- # perun (2)
- # planck (41)
- # re-frame (16)
- # reagent (6)
- # reitit (5)
- # remote-jobs (3)
- # ring (1)
- # ring-swagger (17)
- # shadow-cljs (137)
- # spacemacs (6)
- # sql (4)
- # uncomplicate (7)
- # unrepl (56)
- # vim (27)
re-frame/bidi people, i’m attempting to use a route in views/celestial.cljs and its telling me :celestial isn’t ISeqable. I’m not sure what I’m missing. I’m sort of going in circles at this point. https://github.com/jamalburgess/d-c/blob/auth/src/cljs/d_c/views/celestial.cljs
@decim that error message sounds like you’re giving something a keyword when it expects to get a collection
what line is the error coming from?
I couldn’t see that keyword used anywhere
@danielcompton It ended up being my routes were completely jacked up. Somehow I wrote my main routes without putting them in a vector in routes.cljs (def routes [“/” {“” :universe “celestial” :celestial}])
hey guys, i have some bounty for re-frisk, so if you have interesting ideas please create an issue, thank you https://github.com/flexsurfer/re-frisk, btw there are 2 open bounties if someone wants to contribute
Although I had no problems using plain reagent, using re-frame with an input and trying to input Japanese text using an IME is bugging out a bit
there's a few open React bugs which seem related, but with plain reagent, I wasn't getting the caret-jumping
I recorded a performance profile which contains a caret-jump -- it(s just after the 10000ms point
c-start
core.cljs:163 reframe update value t
core.cljs:163 reframe update value て
core.cljs:163 reframe update value てs
core.cljs:163 c-start
core.cljs:163 reframe update value てsてす
core.cljs:163 reframe update value てsてすt
2core.cljs:163 reframe update value てsてすと
core.cljs:163 c-end
Interesting. There's an extra on-composition-start event being fired when the caret jumps
Got to go home, will try to dig in more tomorrow morning and make a proper issue report. From what I can see, it's pretty consistently that when the caret jumps, there's extra onComponentStart
events being fired on the re-frame controlled input, but I can't get it to happen on the reagent-only input. If anyone has any ideas to try, add to this thread!