pathom

:pathom: https://github.com/wilkerlucio/pathom/ & https://pathom3.wsscode.com & https://roamresearch.com/#/app/wsscode
Christopher Genovese 2021-01-04T01:58:35.078600Z

I've got a pathom resolver (in a Fulcro RAD app) that takes has empty :input and :output that looks like

[{:widget/all-widgets [:widget/id :widget/title :widget/description]}]
My resolver returns data that appears to be a valid tree, of the form
{:widget/all-widgets [{:widget/id "foo" :widget/title "bar" :widget/description "zap"}
                      {:widget/id "goo" :widget/title "car" :widget/description "aap"}
                      ...]}
But the response to the query is empty {} for reasons that are unclear to me. Is there some apparent pathom-based problem with this that might be causing the parse to fail? Thanks!

2021-01-04T08:06:58.080400Z

@genovese are you sure the resolver is not throwing an error? maybe if you could show the code it would be easier to see what’s going on.

dehli 2021-01-04T20:27:05.081600Z

i’ve got this weird behavior where when i query [:a :b] i successfully have both keys returned, but when I query for [:b :a] I get one returned and the other is not found. What’s the best way to debug why this this could be happening? Edit: It looks like it’s something specific to reader3 b/c with async-reader2 i’m not seeing the issue