https://pathom3.wsscode.com/docs/resolvers/#prioritization might help

Priority should help here. I played around with a similar idea of a resolver that would generate and return ids if one wasn’t provided but it was a bit too confusing to debug. I recall caching having an interesting role. If I wanted multiple new ids, my resolver would return the initial cached value. I ended up scrapping the idea before messing with the caching.

Is it possible the client could optionally request tempids? (pco/? :tempids)

Does (pco/? :tempids) work over the wire?

using transit here

the issue is that there are many transformations happening between my client code and server that transform query->ast->query again

oh so it’s a param

that should work I think

I recall it working in an eql query

Something like (pco/? :tempids) operates at the Pathom planner level so it is internal to how Pathom decides when there is sufficient input for a resolver