Fork me on GitHub

hey there, just a general question regarding pathom. how much is that library tied to fulcro? as much as I love the concept behind pathom, I see no real advantage of fulcro over reagent+re-frame, and would rather stick to the later. the thing is that even documentation says We expect that most of our user base is made up of Om Next or Fulcro users, which makes me worry that I will be forced at some point to leak in some fulcro specific ideas into my codebase.


I think that refers mostly to the query "system" (now called EQL) and related concepts (idents, joins etc.)


On your preference to re-frame+reagent I state a new rule based on Greenspun’s tenth rule: Any sufficiently complicated re-frame program contains an ad-hoc, informally-specified, bug-ridden, slow implementation of half of Fulcro. 😂

😛 4

it is not tied at all

☝️ 4

there are some ns-es which require fulcro though for some convenience functions


while it’s a great fit for UI’s, we also use it for IPC


awesome! if so, I need definitely to give it a try.


and we are developing/maintaining a re-frame based Google Chrome extension


alongside a Fulcro SPA


@souenzzo about the timeout, I suggest not using ::pc/key-process-timeout, this is a last resource parser stop, just for real unexpected scenarios, to do timeout you better use core.async, if you use the async parser or the parallel parser, then you can use the core.async timeout for it, example:

👍 4

(pc/defresolver res-with-timeout [_ _]
  {::pc/output [:foo]}
    (let [timeout-ch (async/timeout 3000)
          [ch res] (async/alts! [(async/go
                                  timeout-ch] :priority true)]
      (if (= ch timeout-ch)
        (throw (ex-info "Resolver timeout" {:timeout 3000}))


but this is less cool way to do it, better options are implementing as a resolver-transform ( or as plugin (


@michal as @thenonameguy said, not tied at all, it just provide extra helpers for fulcro users, but we are in the process of trying to get most of those out, with Fulcro 3 coming its been complicated to keep these references, so we want for the user to don't pull anything from fulcro unless you are actually using, so fulcro will be a provided dep probably


@wilkerlucio having dependency on fulcro as optional would be a great step forward 🙂 btw. I really enjoyed watching your presentations about pathom. very inspiring ones imho.


it is, but you have to request the trace as part of the query


@souenzzo add the property :com.wsscode.pathom/trace to your query


the way I do it most of the time is wrapping the fulcro network, pathom has a helper for that:

👍 4

but notice this doesn't work for Fulcro 3, in case you are already using it (the helper thing)


F3 allows for a global eql transform that could handle it, bit that would affect all remotes…wrapping the new remote would also be relatively simple


pfn/trace-remote works with fcn/fulcro-http-remote ?


works with any remote from Fulcro 2


I'm getting

network.cljs:118 Uncaught TypeError: Cannot read property 'cljs$core$IFn$_invoke$arity$1' of null
    at network.cljs:118
    at fulcro$client$network$progress_routine_STAR__$_progress_fn (network.cljc:287)
    at<anonymous> (network.cljc:330)
    at (eventtarget.js:285)
    at (eventtarget.js:383)
    at (eventtarget.js:196)
    at (xhrio.js:904)


Full ex

Uncaught TypeError: Cannot read property 'cljs$core$IFn$_invoke$arity$1' of null
    at network.cljs:118
    at fulcro$client$network$progress_routine_STAR__$_progress_fn (network.cljc:287)
    at network.cljc:275
    at<anonymous> (network.cljc:324)
    at (eventtarget.js:285)
    at (eventtarget.js:383)
    at (eventtarget.js:196)
    at (xhrio.js:873)
    at (xhrio.js:818)
    at (xhrio.js:802)
(anonymous) @ network.cljs:118
fulcro$client$network$progress_routine_STAR__$_progress_fn @ network.cljc:287
(anonymous) @ network.cljc:275
(anonymous) @ network.cljc:324 @ eventtarget.js:285 @ eventtarget.js:383 @ eventtarget.js:196 @ xhrio.js:873 @ xhrio.js:818 @ xhrio.js:802
XMLHttpRequest.send (async) @ xhrio.js:632
fulcro$client$network$xhrio_send @ network.cljc:30
(anonymous) @ network.cljc:334
fulcro$client$network$transmit @ network.cljc:103
(anonymous) @ network.cljs:116
fulcro$client$network$transmit @ network.cljc:103
(anonymous) @ client.cljs:187
fulcro$client$network$transmit @ network.cljc:103
fulcro$inspect$client$handle_devtool_message @ client.cljs:320
(anonymous) @ client.cljs:46
postMessage (async)
(anonymous) @ content-script.js:96


occurs just when there is no p/trace-plugin on server 🙂


just when I'm using 'send to query'