@peeja just replied to your comment in my post. Happy to discuss anything else here

@anmonteiro Ah, cheers!

Won't a key like that only update components that read it?

Ah right, I forgot to continue that thought 🙂

what I do is make the top-level div have that as the react-key

so because the react-key changes, the children of that div will forcibly update

but as I said, it might have bad consequences for local state, I can’t remember and can’t really try it out now

Yeah, I think that rebuilds the DOM and remounts all the components

Should act the same as re-running add-root!

maybe

I didn’t get around to thinking about other solutions, so yours looks interesting

I starred the gist to have a look later, but currently juggling a lot of things

What I posted appears to be working great, but it's liable to break at any React update 🙂

yea

One thing I’ve been thinking about more and more is to just make Om Next work with any VDOM implementation

but I don’t really have the time to even start thinking about what it would take to accomplish such thing 🙂

Dang, that sounds sweet, and also like a ton of work 🙂

Any VDOM in particular you're thinking of? I've never worked with any other than React, and I'm not clear what the others have to offer

yeah, I just saw a Cycle.js demo 2 days ago at a conf

looked really cool but I don’t really know if it would fit Om Next’s use case

I’ve been thinking about it mostly in the context of people that don’t really want to bundle React for its size

there are lighter weight impls out there

Yeah, that makes sense. It seems like React has a lot of code to cover uses that Om code never has, being functional

though if you’re using ClojureScript you probably are OK with a bundle size higher than normal 😛

Fair 🙂

Hey! @anmonteiro, I’ve been using Omify on a project of mine and it seems that the resulting component does not have .-state set which throws an exception in merge-pending-props! when Om tries to (gobj/set cst "omcljs$prev$value" prev). I looked over the omnify! macro and it seem’s there’s no default present for initLocalState.

@gardnervickers: that may well be true, omify is quite dirty at this point, I mostly wanted to prove it could work

Mind opening an issue so we can track that? Thanks!