@dnolen @anmonteiro I like transact! without forcing IQuery - thanks 🙂

It fits in well with a project I'm working on at the moment.

I also like this change a lot!

@jannis: @mitchelkuijpers please note as said above that if you transact! from such a component Om Next will re-render from root unless you specify keys to re-read

That sounds very logical, thnx @anmonteiro

@anmonteiro Noted

@jannis glad to hear it

@dnolen I’m curious what additional problems you had with transform-reads

@anmonteiro turned out to be a PEBCAK

🙂

yeah, tests are passing even with the additional test case you added

yep

Just starting out with Clojurescript and Om. should I learn Om next?

@ujjwalt at this point probably, we’re nearing on a beta and I will probably update the GitHub repo to reflect this in the very near future

like next week

Right. So this is my first attempt at writing Clojure code for production and I wanted to try out the whole thing end to end - Om for front end and Clojure for the backend. Any conventions around that?

Something you could point me to or pointers regarding the general flow

I come from a RoR background and have used Ember for a project.

@ujjwalt if you don’t mind a shameless plug, the team I’m on has been working on a framework that fills out the rest of the full stack interaction around om — see #untangled. It may make more sense to use om without untangled, just depends on what you’re trying to do. I wouldn’t say there are any accepted conventions though, people are still trying stuff out

Well I’m planning on using Om for front end, plain Clojure for the backend and Datomic for storage.

as do we

I didn’t get it

Untangled is a framework on top of Om?

Yes, on the client side. But there’s also a server-side story

Oh

Kindly point me to a resource where I can explore this further

http://untangled-web.github.io/untangled/

Thanks