This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-07-10
Channels
- # admin-announcements (4)
- # beginners (21)
- # boot (85)
- # cider (31)
- # clojure (45)
- # clojure-australia (1)
- # clojure-berlin (2)
- # clojure-dev (7)
- # clojure-italy (10)
- # clojure-japan (17)
- # clojure-norway (8)
- # clojure-russia (2)
- # clojure-uk (15)
- # clojurebridge (1)
- # clojurescript (115)
- # code-reviews (13)
- # core-async (1)
- # editors (17)
- # euroclojure (5)
- # jobs (1)
- # ldnclj (9)
- # off-topic (5)
- # om (18)
- # re-frame (15)
- # reagent (25)
- # sydney (1)
@escherize: You mean like an example of using it?
I’ve not seen one, but it’s not really that hard. I’ll post a gist in a sec
Awesome. That's very kind of you. I've used secretary loads of times, and was interested in how bidi 'felt.' I get a bad feeling about side effect-y code, but it seems like pretty much everyone uses secretary so I havn't had exposure to how the bidi'er's do it
@escherize: I usually do something like this https://gist.github.com/andrewmcveigh/99211f7277271195682d
@escherize: It’s also cool using data-only routes, you can share them client/server so you don’t need to do much to change one.
With the latest Om (version 0.9.0) I get the warning "Don't set .props.children of the React component. Instead, specify the correct value when initially creating the element or use React.cloneElement to make a new element with updated props."
came across this google discussion when I searched: https://groups.google.com/forum/#!topic/reactjs/A9Ul3TXlaOA