I think I understand the bug in the diff just above. transact! on a component with an ident will queue up any other components with the same ident. If those components' paths have changed, but their parents don't rerender (say because a whole chunk of state got moved), they will still have the old paths

so I think the example there is pretty much the simplest reproduction. we have User with an ident, Blog which doesn't rerender, and Author with the same ident which gets a stale path

not sure how to fix the bug except by :pathopt true

maybe it really is a user error, though? you need to make sure parents rerender when paths change?

Complete newbie, any reason why something like (dom/div {:className "test"} "Hi!") doesn't have any attribute? I've tried {:style "stuff"} and others as well, and nothing

The first argument has to be a javascript object, so it's either

#js{:className "test"}

(clj->js {:className "test"})

Oh, great! Could you point me to a recent tutorial then? Things from ~8 months ago are simply broken.

Are you using om now, or om next?

now

(Note that I wasn't using https://github.com/omcljs/om/wiki/Basic-Tutorial because I find it mind-blowingly difficult to follow for some reason.)

I haven't used om now in awhile, so I'm not sure where the latest tutorials are for it.

I'd probably use reagent/re-frame over om now.

oh? 😐

That would just be my preference though.

wondering about (pub)sub

it's tempting to try to do sub in remote reads. but what about unsub?

You can send messages/transactions in componentWillUnmount

It is called when a component will be removed

yes, I am looking for solutions which don't require component lifecycle to know about subscription

there are other cases, too. e.g. set-query!

I would be OK with doing something generic in componentWillUnmount I think

One thing that’s throwing me a little bit in trying to learn Om Next is the argument quoting. For instance, the Quick Start defines a mutate function that looks for an “increment” key, but it’s called like this: (fn [e] (om/transact! this '[(increment)])). Why is it “quoted vector containing a sequence containing increment” instead of, say, (fn [e] (om/transact! this ['increment]))?

This is amazing, no sooner do I post the question than I go back to the “untangled” tutorial, and the next lesson on my list has a note about quoting.

spooky.

@manutter51: That's just the way it is

take a look at https://github.com/omcljs/om/blob/master/src/main/om/next/impl/parser.cljc

Cool, thanks, I’ll check it out

The untangled tutorial also pointed me to the Datomic Pull tutorial, which also explains a lot

http://docs.datomic.com/pull.html

I was just copying the link 😄

😄

also ['increment] doesn't make sense (I think)

how are you gonna throw params in the mix?

Let's say you want to increment with a certain amount

'[(increment {:amount 5})] makes more sense in terms of the standard clojure(script) datastructures

i want to get the uuids that om creates on mutates. are these kept track of somewhere or do I need to listen to some event?

They are stored in the reconciler at [:config :history]

taylor.sando: shoulda thought to log the reconciler. thanks!

taylor.sando: how do you usually associate a UUID with the mutate that created it? I could store it in the app-state along with the mutate but that seems redundant.

I've never actually used the history or undo, I just know that is where the information is.

cool, thanks