Clojurians Log v2

Is there a way to make untangled not trigger a remote read for an entity if it's id is an om/tempid that has not been resolved yet?

Oh I think I might have found my problem, I wasn't returning all the tempids map.

@currentoor: yes, we do exactly that in one niche case

we create data with a new om/tempid but don’t call the mutation that sends to the remote until later

also, there’s an om/tempid? function you can use to check if the id is an om tempid. then conditionally return nil for the remote

oh that's clever

thanks!