Dan Peddle

I'm currently running a single test by renaming the `it` declarations to `xit` [as per mocha API](https://stackoverflow.com/questions/32723167/how-to-programmatically-skip-a-test-in-mocha) and all seems to be ok, given that our tests are self contained....

For a trial run, it seems to me that the trivial implementation on a branch would be enough to play with and do some kind of discovery of whether it's...

would it help if I do some stuff on a fork..? if you can point me at where to start on option 1, that would be enough to get going....

I got as far as invoking it from CLJS, and clearly, it doesn't know what to do with things like `cljs.core.persistentVector` as you mentioned - however, when using `clj->js` recursively...

also, starting to think your third option way up at the top is the best one. IOC / injecting knowledge into generalised library seems the cleanest.

I'll definitely try the lifecycle stuff - also getting handles on the underlying DOM nodes etc - is there an equivalent for `{:ref fn-that-operates-on-DOM}` from react land..? In terms of...

cool stuff, will take a look when it's baked! do you think this API will be stable for a while..?

thanks for the proposal! would you like to take a crack at a PR showing an example?

no, I think I've understood your current pain. I'd be interested in what your solution would look like.

No biggie! Was taking chime for a test drive and these couple of things popped out. While we’re talking, would you mind pushing a release of the version with the...