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 @taion
I can't solve the above question and I'm trying to get your help.
When a loading page is set through a render function, the loading page is always shown regardless of the server's response speed.
However, if the response from the server is very fast, it is thought that rendering the loading page is an unnecessary act, and it is an unpleasant UX.
For example, if response from the server before 200ms after querying, show the next page without rendering the loading page, and if response passed 200ms, show the loading page.
The text was updated successfully, but these errors were encountered:
It's possible in principle, but it's not really straightforward (and it shows the limitations of trying to do this without suspense/concurrent mode).
Are you using Found Relay here?
The rough approach here is that we'd want to modify the resolver such that, instead of immediately yielding the first set of pending elements, that we'd race against a timeout, and only yield them if the "final" elements don't show up in time.
Hi @taion
I can't solve the above question and I'm trying to get your help.
When a loading page is set through a
render
function, the loading page is always shown regardless of the server's response speed.However, if the response from the server is very fast, it is thought that rendering the loading page is an unnecessary act, and it is an unpleasant UX.
For example, if response from the server before 200ms after querying, show the next page without rendering the loading page, and if response passed 200ms, show the loading page.
The text was updated successfully, but these errors were encountered: