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
Hi there! Even if the data is already in cache it shows loading: true and data: undefined on the first render of the route change. In fact the new request to the graphql api is not sending (this is not a problem, just clarifying).
I am not sure the problem is with this package, but I tried to test the issue by creating an app with same logic but with the another package (next-apollo) and there was no problem.
To reproduce the issue I created two sandboxes with the same logic but different packages (next-apollo and next-with-apollo). On the main page it loads "all users", so the data is already in cache when you are changing the route.
Apparently this is because getDataFromTree stopped working in the browser? Is that true @lfades?
I can confirm this is still an issue with "@apollo/client": "^3.0.0-beta.29", but the first log isn't happening. It logs loading false and then loading true. The data is there both times and doesn't seem to flicker on the interface at all or load my loading UI...
Currently none of the 2 packages (or examples in Next.js) is trying to use getDataFromTree in the browser since it was updated to only work in the server, because of its high size, I'm closing the issue because there's nothing I can do from this side and the behavior is the expected (getDataFromTree won't work in a route navigation because getInitialProps gets executed in the browser).
Hi there! Even if the data is already in cache it shows
loading: true
anddata: undefined
on the first render of the route change. In fact the new request to the graphql api is not sending (this is not a problem, just clarifying).I am not sure the problem is with this package, but I tried to test the issue by creating an app with same logic but with the another package (next-apollo) and there was no problem.
To reproduce the issue I created two sandboxes with the same logic but different packages (
next-apollo
andnext-with-apollo
). On the main page it loads "all users", so the data is already in cache when you are changing the route.Codesandbox next-apollo package (correct behaviour):
Logs on route change
Codesandbox next-with-apollo package (incorrect behaviour)
Logs on route change
The text was updated successfully, but these errors were encountered: