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
For example, suppose we have the following nested GraphQL schema and an SPA with a list page that fetches featureA.posts and a detail page that fetches featureA.post.
When navigating from the list page to the detail page, suspense does not occur on the detail page.
(The result of the first useQuery on the detail page is { data: { post: null }, stale: true, ... })
However, when accessing the detail page directly, suspense works as expected because there's no cache for featureA, but I think this behavior is not consistent.
I think this behavior is probably caused by the partial results of schema awareness, but is there a way to make it suspend?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Context
For example, suppose we have the following nested GraphQL schema and an SPA with a list page that fetches
featureA.posts
and a detail page that fetchesfeatureA.post
.When navigating from the list page to the detail page, suspense does not occur on the detail page.
(The result of the first useQuery on the detail page is
{ data: { post: null }, stale: true, ... }
)However, when accessing the detail page directly, suspense works as expected because there's no cache for
featureA
, but I think this behavior is not consistent.I think this behavior is probably caused by the partial results of schema awareness, but is there a way to make it suspend?
Beta Was this translation helpful? Give feedback.
All reactions