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
When fetching the 1st page, fetching === true on both dev and production.
But, when fetching the 2nd page, production says fetching === true, while dev says fetching === false.
Previously, fetching was false on all environment when loading subsequent pages.
I need fetching info to show the skeleton, but I want to do it for 1st page only.
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
-
We've been using urql for years, and it's been serving us quite well this whole time.
However, recently,
fetching
started to behave differently on production, compared to dev environment, for a query that usesRelayPagination
.How pagination is configured:
which is then used to configure cache exchange:
which is then used to configure the client:
The query itself runs like so:
When fetching the 1st page,
fetching === true
on both dev and production.But, when fetching the 2nd page, production says
fetching === true
, while dev saysfetching === false
.Previously,
fetching
wasfalse
on all environment when loading subsequent pages.I need
fetching
info to show the skeleton, but I want to do it for 1st page only.Prod and dev use the same version of urql:
Any suggestions as to what could be the difference?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions