allow bypassing client-side routing on link component #58209
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
arichard-info
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
feedthejim,
ztanner and
wyattjoh
as code owners
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.
Add ability to disable client-side navigation at next/link component level
Use case :
In some cases, it may be wanted to disable client-side navigation on certain internal links :
Why not replace
<Link/>with a simple<a>tag?We could actually replace next/link with simple
<a>tags. But this has several disadvantages:<a>and<Link />do not have the same signature (passHref / LegacyBehavior etc…)Adding a “nativeBehavior” property allows to keep next/link for all internal links, and have fine management of client-side navigation. You can also switch from one to the other very easily