Clojurians Log v2

Is there an example showing an idiomatic way to use :keys returned in the :value of a mutation function? It certainly seems useful, but I haven't found any examples of it actually being used

Related concern: it seems weird that the mutation function, which knows which keys will be stale, only returns hints, and it's up to the transact! call itself to know which keys to re-read. How should I be thinking about this?

You haven't set a key? 😬

It really is just a hint. It’s documentation for you and other people maintaining your code.

AFAIK it doesn’t do anything.

(om/get-computed this) is nil and I can't work out why. Anyone have any theories?

(header-factory (om/computed header {:route route
                                               :menus menus
                                               :start start
                                               :end end}))

What do you do when you have a join like [{:header (om/get-query Header)}} and then header has it's own sub-components with their own sub-queries? In other words, you end up with a big nested join query where the keys have no real meaning other than to pass props down to nested components which have the 'real' query. Has anyone developed any patterns in their parser for dealing with that?

Recursive parser basically.

I can answer my first question, it's because props was nil.

hey guys, anyone is using om-css ? I love the idea and I’d like to have feedbacks

hello there, does anyone know of some up-to-date example of merging data saved in remote back into the om.next app state?

I'm having a hard time figuring what I should pass to the remote callback, especially the way to replace some temporary "record" + om-generated id with its backend version

forget about it, looks like I found my answer in om's tests

I’ve encountered a bug in om-0.9.0 (outlined in https://github.com/slipset/troublems) which is a minimal as I can make it.

As far as I can see, this was fixed in om-1.0.0-alpha18.

I’ve got a workaround for it, so it’s not blocking me at the moment, but I guess it leaves two questions:

1) how production-ready are the 1.0.0-alphas wrt classic om?

2) any chance of having a fix backported to 0.9.0?

@slipset see this comment https://github.com/omcljs/om/issues/765#issuecomment-246989800

TL;DR: yes to 1)

Thanks!