Fork me on GitHub
#untangled
<
2016-07-15
>
currentoor17:07:13

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?

currentoor17:07:06

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

ethangracer18:07:39

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

ethangracer18:07:16

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

ethangracer18:07:05

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

currentoor18:07:39

oh that's clever