Fork me on GitHub
#om
<
2015-07-10
>
escherize13:07:33

Is there a reference implementation of bidi, in cljs?

andrewmcveigh13:07:17

@escherize: You mean like an example of using it?

andrewmcveigh13:07:28

I’ve not seen one, but it’s not really that hard. I’ll post a gist in a sec

escherize13:07:29

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

samueldev13:07:22

bidiers (noun)

andrewmcveigh14:07:20

@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.

jonas16:07:29

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."

jonas16:07:35

Is this harmless?

samueldev17:07:11

I came across that as well

samueldev17:07:18

It's a React warning, not an Om warning

samueldev17:07:41

came across this google discussion when I searched: https://groups.google.com/forum/#!topic/reactjs/A9Ul3TXlaOA

dnolen17:07:56

@jonas harmless and we can’t really do anything about it until 0.14 very likely

jonas17:07:26

dnolen: ok, thanks!

dnolen17:07:38

there’s a lot of warnings that get triggered because the code would be a mistake for a JavaScript user