docs: Add missing deprecation notice for legacyBehavior in Link component #78405
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.
What?
The Pages Router section of the Link component documentation now clearly states the deprecation notice for the
legacyBehavior
prop.Why?
The Pages Router documentation was missing the deprecation notice that appears in the App Router docs, which could lead developers to continue using a feature that is scheduled for removal in Next.js v16.
How?
Added the deprecation notice to the
legacyBehavior
section in the Pages Router part of the documentation, making it consistent with the notice already present in the App Router section. The notice clearly states that the prop will be removed in Next.js v16 and provides information about migrating to the new behavior.Fixes #78381