Fork me on GitHub

Fulcro 3 remotes are just maps…you could easily write one to use the f2 pathom remote @souenzzo


I should probably make a function that does so…it’s a generic transform from one interface to another


Ah, but it will bring f2 onto your classpath I guess, so it would need to be a separate lib or something


which i’m not going to do 😜 Basically f3 remote is a map with :transmit! key that is a function that gets a send node (a map). See the implementations in F3. Just adapt that to proxy over to the f2 remote’s send method, and pass callbacks that adapt the response.


Once you’ve done that, publish it for everyone else 😄


I implemented it But I'm a bit unsure about this impl. the :com.wsscode.pathom/trace isn't working on inspect Need some docs about which keys we should pass to result-handler It's really hard to find in the "main" impl with keys are passed to result-handler


inspect will need upgrade, since it has to detect network type and augment it (so it can transform the query to add the trace property to the request)


oh, maybe not, this may need to go in fulcro code since the wrappers live in fulcro now


@U0CKQ19AQ I'm remembering now that this changed right, there is no more wrappers? sorry @souenzzo, I'm not close enough to this code to give you proper guide, would have to look again and understand the new integration better


See default remote. I know it’s a bit of tracing, but it is really just this:


That’s the format of the value passed to the result handler


(let [tx {:type :root, :children [{:type :prop, :dispatch-key :foo, :key :foo}]}]
  {:transaction      tx
   :outgoing-request request??
   :headers          {}
   :body             (parser (eql/ast->query tx))
   :status-code      200
   :status-text      "ok"
   :error            nil
   :error-text       nil})
Can I use nil on request?


yeah, just drop that key

👍 4

I think the only things that the built-in stuff uses is body and status-code and transaction…the other stuff is for extra info