There is a plan to make #pathom expose graphql. I'm (as me, not as pathom contributor) planning to work on that in some days.

just to clarify this statement, pathom is already able to consume graphql apis, but not to expose then as GraphQL

have not tried it. Tools deps doesn’t work well on windows, unless you use the ubuntu support.

and you need npm etc.

but I don’t see any specific reason why windows would be out

I think you’d have to use the Ubuntu support to get a clojure command line working.

you can also just move the deps into project.clj, and forget about deps.edn

I wonder if anyone has tried https://clojure.org/guides/getting_started#_other_ways_to_run_clojure on windows

Your use of pathom’s placeholder syntax is confusing and discouraged (by me).

otherwise you can certainly load into the root if you want

@U0CKQ19AQ is there a better way to do what I am trying to do then? My App component holds a query that needs to be run at the top-level in Pathom

why not define a resolver that has a simple key and no inputs? Those are root queries

@U0CKQ19AQ So you mean define a :app resolver? Because here is the query I have in App:

{:query [{:all-users [:user/id :user/name]}
           {:current-user ...}]}

but df/load takes a parameter which defines the query it runs

I’m not sure where the disconnect is…all the placeholder does is “stay in same context” which you weren’t even in…so AFAICT you’re not doing anything but confusing the reader

@U0CKQ19AQ sorry, I would like to not use a placeholder, but I simply don’t understand how to achieve the same result without one. As far as I understand when I issue a (df/load app :some-query SomeComponent), it runs :some-query in the root context with the selection defined by :query in SomeComponent

But in my scenario the selection defined in SomeComponent is what I want to get on the root context

so what should go in place of :some-query?

if what you’re doing works, perhaps I don’t understand it…I don’t have more of an answer for you. Load always load to root. Period. What you call the keyword is what it appears as. Period. If you’re targeting, then that is something else.

I honestly don’t remember 😜 it could have been the force-children thing. It depends on how you want to use the components. Fulcro generates React-compatible things, but children end up as a lazy sequence sometimes, and react doesn’t know what to do with those. If you remember to force the children, then you’re probably ok using their factories.

So i have been playing around with using force-children. I tried your react-motion demo project and got to see what happens when the lazy error or with-context error are present. The behavior I am seeing is a bit different, It appears to render fine but without styling, and the functionality doesn't work properly... I might make a git repository showcasing the problem and post it here if that is ok.