This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-09
Channels
- # admin-announcements (6)
- # arachne (3)
- # beginners (66)
- # boot (84)
- # braveandtrue (1)
- # cider (84)
- # cljs-site (1)
- # cljsjs (3)
- # cljsrn (2)
- # clojure (138)
- # clojure-austin (2)
- # clojure-czech (1)
- # clojure-gamedev (6)
- # clojure-germany (15)
- # clojure-italy (2)
- # clojure-russia (26)
- # clojure-uk (51)
- # clojurescript (97)
- # css (1)
- # cursive (1)
- # datascript (13)
- # datomic (6)
- # devcards (2)
- # docker (1)
- # emacs (5)
- # hoplon (9)
- # immutant (5)
- # jobs (4)
- # leiningen (6)
- # luminus (27)
- # mount (4)
- # om (16)
- # om-next (4)
- # onyx (15)
- # other-languages (36)
- # overtone (1)
- # proton (3)
- # quil (1)
- # re-frame (11)
- # reagent (24)
- # rum (4)
- # spacemacs (3)
@dnolen: In Om Next, instrument
is only ever called for the root component, as opposed to om.core
’s instrument which was called for every build
down the component tree. is this intentional?
I would expect it to be called whenever we called a factory function
@anmonteiro: pretty sure I didn’t fully bake instrument
at all yet, so probably nothing intentional there
@dnolen: gotcha. I think that’s the only obstacle to fully make it work. Everything else seems to be in place
I noticed it by going over the devcards example
@anmonteiro: ah, k - yeah if the patch is simple - then def welcome
@dnolen: thx, I’ll see what I can do
@dnolen: I’m very new to Om Next, looking through todomvc demo, it seems to me this part doesn’t work https://github.com/swannodette/om-next-demo/blob/master/todomvc/src/cljs/todomvc/core.cljs#L69 basically I can’t add new items. Is this intentional and left unfinished as a learner's exercise, or am I missing something?
@ag: yes that TodoMVC is not fully functional
Question, ya’ll, about parent child relationships in om.next: If a child component needs access to a parents’ props, what’s best way to go about it? 1) Access parent via query (e.g. [:answer/id {:question [:question/id]}])
, 2) Pass the parent down the chain (e.g. (answer-component {:question …})
, or 3) Don’t do it – just pass the parents’ necessary fields (e.g. (answer-component {:question/id 1}
). I hope that makes sense...
I’ve begun using #1, however, I’m frequently running into situations that remind me of bad situations in React: child components knowing too much about their parents are brittle.
I think I’m leaning towards #3… Thoughts?
Anyone have an idea on how to implement http://api.jquery.com/slidetoggle/ with CLJS/Goog code.
I would use a CSS transition triggered by adding/removing a class (or attribute, if that fits your style better).
If you want to hide the element afterward, you could listen for the transitionend event.