Fork me on GitHub
#fulcro
<
2018-10-27
>
currentoor00:10:56

I’m see strange behavior with tempid mapping, on the server i’m returning this tempid remapping

#:fulcro.client.primitives{:tempids {#fulcro/tempid["22e6d9c7-e6eb-4c0f-beb9-d074f13c9037"] 17592186045433}}

currentoor00:10:13

which looks correct, but in the client in fulcro inspect i see this

currentoor00:10:00

it’s as if the pathom parser looses the tempid encoding of the tempid

currentoor00:10:17

@wilkerlucio do i have to do anything special with pathom to make it understand fulcro tempids?

pvillegas1200:10:09

@currentoor are you using transit?

currentoor00:10:48

fulcro’s transit built into the websockects components

wilkerlucio03:10:56

@currentoor usually you have to request that on the query, to avoid that there is a feature in pathom to always request it

currentoor16:10:35

Ah yeah that seems like the issue

currentoor16:10:47

Thanks @wilkerlucio

eoliphant18:10:59

hi i'd asked about this before, but got pulled into some other stuff and didn't have a chance to play around with it much. when calling a JS API that's not the server (e.g. 3rd party auth), I was looking at doing something like

(defmutation call-auth0-cognito-whatever
  ...
  ; set stuff like :ui/loading, etc in state
  (-> (invoke-api ..)
        (.then .. #(success-mutation))
        (.catch .. #(error-mutation))
I recall someone mentioning pathom as a more sophisticated way to do this as well. But just want to make sure i'm on the right track