This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-02
Channels
- # admin-announcements (1)
- # alda (3)
- # beginners (28)
- # boot (155)
- # braid-chat (8)
- # cider (22)
- # cljs-dev (46)
- # cljsrn (24)
- # clojure (94)
- # clojure-belgium (23)
- # clojure-czech (2)
- # clojure-germany (7)
- # clojure-greece (12)
- # clojure-india (1)
- # clojure-japan (1)
- # clojure-russia (118)
- # clojure-spain (18)
- # clojure-spec (40)
- # clojure-sweden (19)
- # clojure-taiwan (4)
- # clojure-uk (5)
- # clojurescript (185)
- # clojutre (10)
- # community-development (5)
- # core-logic (11)
- # css (5)
- # cursive (7)
- # datomic (5)
- # dirac (6)
- # emacs (2)
- # euroclojure (1)
- # events (5)
- # hoplon (355)
- # instaparse (3)
- # jobs-rus (5)
- # lein-figwheel (2)
- # leiningen (5)
- # mount (11)
- # off-topic (8)
- # om (20)
- # onyx (10)
- # other-languages (87)
- # perun (9)
- # proton (1)
- # re-frame (21)
- # reagent (16)
- # specter (28)
- # tmp-json-parsing (5)
- # untangled (19)
- # yada (43)
@dnolen: was looking through the issues, and I think: - #679 has been fixed - #674 is just a question that has been answered here in slack
@anmonteiro: thanks for the heads up will take a look
@dnolen: while you鈥檙e at it, pretty sure #693 is also just a question that could be answered here
Hey! Is anyone here using the latest om alpha and devcards 0.2.1-7 in the same project? They ship different React versions. I'm wondering how to avoid conflicts there.
@isak: It did work and would've solved my problem if another, pure JS component hadn't been pulling in React once more. Thanks 馃檪
Ok, I made an ackward false alarm for a bug on github issue page https://github.com/omcljs/om/issues/693#event-680175746, could someone here notice any pitfall I'm falling trough, trying to getElementById, after html code is fetched from remote server via http/get request? After a tip from anmonteiro, I used :remote and :send of the reconciler to handle my async callback, but I still get the same problem, that the browser wont find the element. If anyone has time to look at the issue I made and tell me where I'm wrong, it would be great. Otherwise, no problem (knowing how few heros actually take their time to help, a topic for another discussion).
@hlolli: I looked at your example and I believe that your problem is due to the fact that you render once without the remote data so the svg is not yet in the page
so maybe try 2 things:
- check that the SVG is actually there when you query for the DOM node
- move the code to componentDidUpdate
when the remote data will already be there
ok, I by the way, also tested putting the svg in a local def and dangerouslysethtml straight from the (cljs)string. And then it worked, it always finds a dom element, just not when trought the async go loop.
@anmonteiro: If you have a sec can you look at this? https://github.com/omcljs/om/pull/691
@anmonteiro: ok, I also tried to do if mounted? then...
. But I think i will just try to find some ways of making a boolean check that the element exists before assigning a js-fn to it. So I maybe ask again tomorrow (this is work related issue and I'm at home now 馃檪 )
@cmcfarlen: I鈥檒l put that on my queue, just can鈥檛 get to it today
@anmonteiro: np. Thank you.