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
We have a table component where fragments for individual cells are deferred with the @defer directive. On the initial load of the table, we see these cells suspend and fall back to their parent suspense boundary's fallback value. However, on calls to the loadNext function returned by usePaginationFragment, we see these cells render and the call to useFragment reads undefined rather than causing the component to suspend. However, using the refetch function returned by usePaginationFragment I do see the cells with the deferred fragment suspend successfully.
Below is a simplified example of the components and fragments I'm working with when experiencing this behavior:
We have a table component where fragments for individual cells are deferred with the
@defer
directive. On the initial load of the table, we see these cells suspend and fall back to their parent suspense boundary's fallback value. However, on calls to theloadNext
function returned byusePaginationFragment
, we see these cells render and the call touseFragment
readsundefined
rather than causing the component to suspend. However, using therefetch
function returned byusePaginationFragment
I do see the cells with the deferred fragment suspend successfully.Below is a simplified example of the components and fragments I'm working with when experiencing this behavior:
example responses from queries fired by our calls to load query, load next, and refetch are below
load query:
load next:
refetch:
The text was updated successfully, but these errors were encountered: