This code results in an internal guardrails exception in the latest Pathom3. I'm not sure if specifying a key path in ::pco/input
is proper usage. In fact, if I trim the path in each of the resolvers to a single key (ie, :ui/query
and :pql/query
) , pathom is happy. Further, if I remove one of the resolvers, pathom is happy.
With guardrails disabled, Pathom3 has throws a stack overflow. This is the first many frames
(sorry for the delayed reply - I got distracted yesterday)
Fantastic thanks!
the issue was a recursion in the nested thing, the edge of ui-query->time-range
input was the same key as the output (`:query/timeRange`)
that drover the planner to do an infinite recursion, but fixed now
thanks for testing and bringing those cases to the light 🙂
from your description it seems a bug somewhere, what happens if you disable guardrails? the result is what you expect?
I haven't tried disabling guardrails - I'll give that a shot in an hour or so