feat(blog): Router article for lane loader rewrite - #1134
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
||
| One call, one promise, one destination. | ||
|
|
||
| Now imagine that the user hovers the link first. The router starts preloading `/account`. They click while its loader is still running, so the navigation joins the work that the hover already started. |
There was a problem hiding this comment.
we show the imperative API above, now we mention Link hovering
There was a problem hiding this comment.
i agree, but then I thought that if we show <Link to="/account"> then it feels less like an action so i didn't really know how to set this up better
| </figcaption> | ||
| </figure> | ||
|
|
||
| A **lane** is a private, unpublished draft of the matched route branch. Reading from left to right: |
There was a problem hiding this comment.
we should introduce the lane concept (analogy, ...) before using it
| These steps are not one long waterfall. The pending timer races the loaders. Normal route components can load alongside them. A framework render can be in progress while the private lane continues toward its final result. | ||
|
|
||
| > [!NOTE] | ||
| > `Promise.allSettled` is shorthand here. The router waits for the outcomes needed to choose between success, failure, and redirect.[^reduction] |
There was a problem hiding this comment.
what is this referring to?
There was a problem hiding this comment.
it's in the image above it
2 participants
No description provided.