Fork me on GitHub
Björn Ebbinghaus13:11:50

@wilkerlucio Do you know why the parser sometimes needs exactly 3s + the usual resolve time when I do not return a queried attribute and that is therefore set to :com.wsscode.pathom.core/not-found ?

Björn Ebbinghaus13:11:27

This happens every two to four queries and I don't know why.

Spencer Apple16:11:19

I want to send a broadcast to via websocket with the updated information during a mutation. Where do you think in the pathom / fulcro stack the best place to do that is? I have no problem actually sending data via fulcro websocket’s push, I just am not sure the best place to call the push fn inside of pathom. 1. My first thought was just using the :parser in the env of a mutation to kick off an additional query and keep all the logic in the mutation. That didn’t work though as all my queries using the :parser in the env gave me a :com.wsscode.pathom.core/reader-error (which I don’t know how to debug). 2. Then I was thinking I could add a ::pc/transform function to mutations I want to broadcast, but I still am not sure which parser I can use to do that. 3. Also I could go the route of adding a tx-report-monitor or an atom watcher and broadcasting those changes on an async flow. Thanks for all your great work, and am curious of your thoughts