Fork me on GitHub
#pathom
<
2021-09-16
>
Drew Verlee16:09:03

In Pathom viz why do some of the indexs show up as different colors in i the "Index Explorer" tab?

wilkerlucio17:09:28

purple: attributes blue: resolvers orange: mutations

wilkerlucio17:09:35

is these colors you talking about?

Drew Verlee18:09:28

yes they are ty ty

Drew Verlee16:09:58

Whats an example of something that would go in Query > "Entity Data" ?

dehli17:09:37

Entity data allows you to query for resolvers in pathom-viz and provide data to the resolver (or upstream resolvers). For example, let’s say you only have the following resolver:

(pc/defresolver full-name
  [{:user/keys [first-name last-name]}]
  {:user/full-name (str first-name " " last-name)})
If you were to query for [:user/full-name] as a top-level key, you wouldn’t get it back b/c :user/first-name and :user/last-name are needed as inputs (and pathom can’t get to either of those attributes to fulfill the inputs of :user/full-name ). You can inject those keys via entity data :
{:user/first-name "Jane"
 :user/last-name "Doe"}
and then when you query for [:user/full-name] you’ll get {:user/full-name "Jane Doe"}.

👍 2
wilkerlucio17:09:02

yes, entity data is top level provided data

wilkerlucio17:09:17

note the auto-complete (in the query part) is sensitive to it, if you change the data it will affect the auto-complete options (considering the provided data)

🚀 4
JonR22:09:58

I'm using Pathom + Walkable in a new SPA (not Fulcro). I'm wondering about client said query caching and have been google around the react world at stuff like https://react-query.tanstack.com/. Does anyone have any suggestions for resources or know of a cljs/pathom existing solution?

lilactown22:09:50

I think Fulcro is state of the art atm