Fork me on GitHub
#pathom
<
2021-02-05
>
markaddleman16:02:07

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.

wilkerlucio17:02:42

from your description it seems a bug somewhere, what happens if you disable guardrails? the result is what you expect?

markaddleman17:02:12

I haven't tried disabling guardrails - I'll give that a shot in an hour or so

markaddleman15:02:34

With guardrails disabled, Pathom3 has throws a stack overflow. This is the first many frames

markaddleman15:02:17

(sorry for the delayed reply - I got distracted yesterday)

markaddleman17:02:45

Fantastic thanks!

wilkerlucio17:02:42

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`)

wilkerlucio17:02:55

that drover the planner to do an infinite recursion, but fixed now

wilkerlucio17:02:24

thanks for testing and bringing those cases to the light 🙂