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 navigating to the collection detail page from the explore page, the properties filter component is first displaying the list of collections instead of directly the properties filter. This happen pretty quickly:
From explore/collection:
Screen.Recording.2023-11-21.at.10.16.36.mov
When the query to fetch the collection is already cached, (first navigation start on the explorer/nft page), the list of collection is clearly visible:
Screen.Recording.2023-11-21.at.10.17.12.mov
This behaviour doesn't happen when reloading the collection detail page, but I notice the properties are not initially display (no SSR), and are only fetch client side:
Screen.Recording.2023-11-21.at.10.20.38.mov
My guess is there is a/multiple useEffect somewhere that prevent the initial loading to display the right stuff.
The text was updated successfully, but these errors were encountered:
When navigating to the collection detail page from the explore page, the properties filter component is first displaying the list of collections instead of directly the properties filter. This happen pretty quickly:
From explore/collection:
Screen.Recording.2023-11-21.at.10.16.36.mov
When the query to fetch the collection is already cached, (first navigation start on the explorer/nft page), the list of collection is clearly visible:
Screen.Recording.2023-11-21.at.10.17.12.mov
This behaviour doesn't happen when reloading the collection detail page, but I notice the properties are not initially display (no SSR), and are only fetch client side:
Screen.Recording.2023-11-21.at.10.20.38.mov
My guess is there is a/multiple
useEffect
somewhere that prevent the initial loading to display the right stuff.The text was updated successfully, but these errors were encountered: