Skip to content

Conversation

@maryhipp
Copy link
Contributor

Need to keep suspense loading state so that $client is created correctly in time for API requests
Do we need to keep the more global isAppReady stuff?

@psychedelicious
Copy link
Contributor

Because the isLoading boolean is true whenever images are loading, the <LoadingGallery /> component was swapped in whenever you load more images / scroll, and it only ever showed 20 skeletons.

Fixed this by appending 20 dummy items to the images array, and displaying a skeleton within the virtuoso component instead. Now it displays however many images area already loaded, followed by 20 skeletons if loading. On first load, it still displays 20 skeletons while loading.

@psychedelicious
Copy link
Contributor

I don't think we need any of the is ready stuff, it all seems to work fine for me on this PR

@psychedelicious psychedelicious enabled auto-merge (rebase) July 2, 2023 01:55
@psychedelicious psychedelicious merged commit 0e50005 into main Jul 2, 2023
@psychedelicious psychedelicious deleted the maryhipp/skeleton branch July 2, 2023 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants