Fork me on GitHub

What is the setup for async dynamic resolver? I tried to make an async version of a working dynamic resolver, but the resolver seems to be executed only once and I don't know why


another question: I have this ident query [{[:a/id 1] [:a/x :a/y]}] against a dynamic resolver. But the first call to the function has env's :dispatch-key being :a/x while I expect it to be [:a/id 1] (meaning: one level up). Is that intended behavior? What's the recommended way to detect such case because I usually infer from :dispatch-key?


there is a new data point in the reader3, which is :com.wsscode.pathom.connect.planner/node (on the env), this contains the planner data about the call, you should look into this instead of :ast


@wilkerlucio is there any util functions to convert an index-io to index-oir? (with a fixed resolver sym, of course)


not possible, they may not match, and have different considerations, so you have to make each differently


consider index-io is used only for auto-complete (which is important), but things should still work without it


I figured out I'd better stick to pc/add and have all indexes generated