Clojurians Log v2

Hey all, trying to build pathom-viz on windows here and it looks like in order to get shadow to actually compile I had to run:

npx shadow-cljs --aliases dev:dev-ws:electron:provided release electron-background electron-renderer

./script/build-electron

hey everyone, what’s the preferred way to inject query data that’s already been resolved in a parent/sibling key into a child query input? attempting to put the relevant key on my input declaration doesn’t seem to be working

I figured it would be possible to do something like ::pathom-connect/input #{:user/email :other-thing/id} but that doesn’t seem to be the case

@mss if I get right, what you need is to place the data in the output of the parent, so it will be available for children

the input is a declaration of requirement, the data needs to come from somewhere, can you give a small example of what you are trying to do?

yeah so I have a fulcro load! call on app startup that’s parameterized by :user/email like so:

(df/load! mounted-app
 [:user/email user-email]
 User...)

this a good time to debug just your parser, use the REPL and make calls direclty to it, use * on the query to see all the data available at that point

this way I usually can spot where the data is missing

@wilkerlucio having several problem with the new pathom-viz app, it’s constantly locking. couldnt’ really see anytyhing in the console log. how can i debug it? i noticed that everytime i paste something app blocks, this is not the only case though.

you can open the devtools with cmd + opt + i (on mac). or ctrl + alt +i on others

what OS are you in?

and you mean pasting at the query editor?

mac (bigsur), dont’ really see anything on the devtool, it just freezes when writing the query

yes, pasting at the query editor. but it’s freezing also when comlpeting a query with an input. example, i am trying to type this

[{[:edge.calendar/code "{{code}}"] [:edge.calendar/name :edge.calendar/code   :edge.calendar/calendarid  :edge.calendar/creation-date :edge.calendar/expired
                                                                    :edge.calendar/status :edge.calendar/workdays  :edge.calendar/weekend
                                                                    {:edge.calendar/events [:edge.calendar.event/day :edge.calendar.event/type :edge.calendar.event/label]}]}]

[{[:edge.calendar/code "acode"] []}] 

this is against a pathom2 engine

saw this is in the console when connecting to the remote

main.js:2441 POST <http://localhost:3000/pathom> 500 (Internal Server Error)
h	@	main.js:2441
l	@	main.js:2442
$APP.cljs.core.async.impl.ioc_helpers.run_state_machine	@	shared.js:7233
$APP.cljs.core.async.impl.ioc_helpers.run_state_machine_wrapped	@	shared.js:7234
(anonymous)	@	main.js:2443
$APP.cljs.core.async.impl.dispatch.process_messages	@	shared.js:7166
processImmediate	@	internal/timers.js:439

no error when the app freezes, just when connecting to the remote

the engine shouldn't matter because the calculations happen inside the app for auto-complete

I didn't upgraded to Bigsur, but I heard about some general complaints on performance, I wonder if the version of Electron (which is not very recent) is getting affected by it

might be, i didn’t use pathomviz since upgrading to big sure, let me check if the older version of PathomViz has the same issue

cool, thanks for checking, curious to learn of your findings

no problem with 1.1.1

pasting works, query i was trying to enter works fine

so i think something it’s going on with the latest version. i am happy to help test it, not sure how though :/

is it a big index? I did changed the auto-complete algorithm, but I personally only tested on small things, it can it

no, it’s not big at all

if you have some time to help with debug, you can build the app locally, and try there, using the performance tools from Chrome, in the dev app you will be able to see the names of the functions

have you used the performance tab from Chrome before?

(and just to give you context, even if the algorithm was slower, there is a bunch of caches, so it should be slow only for the first letter, after that its the same, so I wonder if the cache is misconfigured)

or maybe its something else entirely

could it be the cache from the prev version interfering with the latest? ill remove it and try again

no, this cache is memory only

ok, will check the performance tab and send you my findings.

this a screenscast with the issue

yeah, and the view is strange too, it shouldn't be black on the right side

how is the style after you run a query?

the black is the console

before that, the query results pane part

(dark theme)

ohh right

for comparison here

dark theme shouldn't affect it (unless there is something I dont know about Codemirror6 and Bigsur :P)

@mss in pathom3, placeholders do that https://pathom3.wsscode.com/docs/placeholders in pathom2, you can use :pathom/context special params Your query should look like that:

[{([:user/email "abc"] {:pathom/context {:other-thing/id 42}})
  [:user/something]}]

@wilkerlucio what specifically would I be looking for? my query is calling the correct resolver unless I put in the key :user/email in the input set like so:

{::pathom-connect/input  #{:user/email :task/id}
   ::pathom-connect/output [:task/title
                            :task/description]}

I would think that since :user/email is both a key satisfied by a query parameter/ident and returned into the response map at my top level user resolver that it would be available as an input key to child resolvers

FWIW my query looks something like this:

[{[:user/email "<mailto:testuser@test.com|testuser@test.com>"]
  [:user/first-name 
   :user/last-name 
   :user/email
   {:user/projects
    [{:project/goals
      [:goal/id
       {:goal/tasks
        [:task/id
         :task/status]}]}]}]}]

(pathom-connect/defresolver user [env params]
  {::pathom-connect/input  #{:user/email}
   ::pathom-connect/output [:user/first-name
                            :user/last-name
                            :user/email]}
  {:user/first-name user-first-name
   :user/last-name  user-last-name
   :user/email (:user/email params)})

I would have expected that :user/email would then be available in child resolvers

the ident only provides data to the first child level of it, after that each context has only the data provided for it

you can flow the data down manually if you want, but seems too many levels for me

another option is have a path to fetch the user id from the task id (if it has a reference to one)

What would a path to fetch the user id look like? Something out of band? My initial way of solving this was to reach for storing global data like that in the request and throwing it into the parse env. Is that the best way to go about that?

yeah unfortunately within the task resolver there’s no context around what user id exists. I tried to assoc the user/email into the env within the user resolver, but that didn’t seem to work

it depends on how you data is organized, does your db row/entity for task knows about the user related to it?

does it have a reference to it?

a path is just a resolver that gets :task/id and outputs :user/id, pulling that relationship from your database

but this also depends if your data model a task has a single ID, or if its something else

The task knows nothing about the user, unfortunately. It’s currently designed as a one way relationship from users to projects to goals to tasks

in this case I suggest you do the manual forward down of the user id

for example, in the reoslver for :user/projects, in each item you add the :user/id you got on that resolver input

then you do the same for :project/goals, then same for :goal/tasks, makes sense?

Yep, absolutely. Really appreciate the insight here. And thank you for all the work you’ve done w pathom — it’s phenomenal software