-
Notifications
You must be signed in to change notification settings - Fork 0
⚡ Bolt: optimize data fetching in project detail page #25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
aicoder2009
wants to merge
2
commits into
main
Choose a base branch
from
bolt/concurrent-fetch-project-details-8927063821569846899
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+43
−38
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| ## 2025-02-28 - [Concurrent Data Fetching] | ||
| **Learning:** Sequential data fetching can significantly increase page load latency. Combining independent fetch requests using `Promise.all` allows them to process concurrently, preventing network waterfalls. | ||
| **Action:** When implementing page components that require multiple independent data streams, analyze if they can be fetched in parallel using `Promise.all` rather than using sequential `await fetch()` calls. |
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using
Promise.allfor all three fetches makes the whole load fail if any request rejects or JSON parsing fails (e.g.,/api/liststransient 500), which is a behavior regression vs the prior sequential flow where the project could still render and only lists would be missing. Consider fetching/parsing the project first (or usingPromise.allSettled) and only treating the project request as fatal; handle lists/all-lists failures independently (e.g., keep project visible and show a non-blocking error banner).