https://clojurians.slack.com/archives/untangled/p1489701908122380

Just to verify - should I expect to get back resolutions to both tempids for my widget requests if I have a transaction with two mutations named the same thing? Or does one end up overriding the other?

@therabidbanana hah, I was thinking about that behavior a week or 2 ago

yeah, the result of mutations is a map so the same symbol will be overridden

Okay, so it's not an underlying bug in untangled, but just how the om parser itself works right now?

I can pretty easily create a new mutation to work around it, just seemed straightforward to map over my list of tempids (and other parameters) to create a combined transaction rather than a new mutation

it’s om next behavior

would have to think about whether it’s a bug or not

Yeah - I could see it going either way. It's just that I expected it to work because it felt like it should with transactions being data and all. 🙂

But in the end it is probably encouraging me to a better pattern of a combined mutation to represent this case, so I can see it going either way

Any thoughts on the next steps for this PR ? https://github.com/omcljs/om/pull/857 The aim is to allow dynamic queries (i.e. set-query for datascript backed state) The next step is to integrate with get-query, set-query, thoughts/comments welcome.

What is the :component used for in query metadata?

hello guys, this is an article I just wrote on making draggable elements with om.next => https://medium.com/@baptistedupuch/building-drag-and-drop-elements-with-om-next-836cff477b72#.14m1zl4sv

please give me feedbacks as I am still new to om.next

@foobar The :component is used for normalization: when a component class has an ident, the data that part of the query fetches is moved into a table and referenced with a link.

It may be used for other things too, but that one comes to mind