Does this help? https://edn-query-language.org/eql/1.0.0/specification.html#_recursive_queries

It’s relatively straightforward

https://pathom3.wsscode.com/docs/eql/#recursive-queries

Well how do I tell Pathom that the output of the resolver is a nested tree?

So obviously you can make a resolver that has the output [:id {:children [:id]}]

that resolver can answer a recursive query…

But it will be called for each node once. And I get the whole tree in a single DB query.

if you return the entire tree pathom will just return it and not continue calling the resolver

i've used that in the past as an optimization - calling db/pull directly instead of having nested pathom calls

If you want to keep the decomposition into resolvers, you can also leverage batching in pathom3. let's say you have a resolver that gets a list of IDs, one that gets the attributes, and maybe a nested one that gets nested attributes from the db It will only take 3 queries, 1 per resolver, if you write batch queries In pathom2 that wasn't working for nested attributes