initial React.Suspense support in client
#130
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…p name, updating reat-query usage
…ent of tanstack/query + paginated-data-table to work half-correctly with Suspense.
…server component rework
…ed more default exports.
This was referenced Jul 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #32, #40, #17, #124, and #129
Summary
This PR added:
React.Suspense+ tanstack useSuspenseQuery support to:/block/[ht]/transaction/[hash]/blocks/transactions/blockand/transactionpaginated-data-table.tsxcomponent and howTransactionsTableandBlocksTableconsume it + use tanstack/tableThis PR was painful. A lot of small logistical stuff with how queries were structured and used + poor documentation but the UX/UI of the client has benefited greatly from it.