You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
makeWrapPlansPlugin can be confusing because it wraps the plan before the argument plans have been applied.
Let's say someone wanted to add a plan wrapper plugin to reject requests where the "limit" of a fetch was too high. How could we see the size of first/last when they've not been applied yet (without relying on argument names).
Also, in this case we'd probably want to raise the error from nodes rather than from allRows since {allRows{totalCount}} without pagination limits is a perfectly reasonable query, whereas {allRows{nodes{id}}} would not be.
The text was updated successfully, but these errors were encountered:
makeWrapPlansPlugin
can be confusing because it wraps the plan before the argument plans have been applied.Let's say someone wanted to add a plan wrapper plugin to reject requests where the "limit" of a fetch was too high. How could we see the size of
first
/last
when they've not been applied yet (without relying on argument names).Also, in this case we'd probably want to raise the error from
nodes
rather than fromallRows
since{allRows{totalCount}}
without pagination limits is a perfectly reasonable query, whereas{allRows{nodes{id}}}
would not be.The text was updated successfully, but these errors were encountered: