Docs: Inline documentation for the 'legacyBehavior' property seems to specify an incorrect default value

[haykam821]

What is the improvement or update you wish to see?

These two documentation sources seem to conflict:

next.js/packages/next/client/link.tsx

Lines 79 to 83 in ba02680

	/**
	* Enable legacy link behaviour.
	* @defaultValue `true`
	* @see https://github.com/vercel/next.js/commit/489e65ed98544e69b0afd7e0cfc3f9f6c2b803b7
	*/

next.js/docs/api-reference/next/link.md

Line 53 in ba02680

- [`legacyBehavior`](#if-the-child-is-a-tag) - Changes behavior so that child must be `<a>`. Defaults to `false`.

From my testing, the latter documentation is correct.

In addition, some other inline documentation appears outdated based on the now-default experiment flag:

next.js/packages/next/client/link.tsx

Lines 85 to 99 in ba02680

	// e: any because as it would otherwise overlap with existing types
	/**
	* requires experimental.newNextLinkBehavior
	*/
	onMouseEnter?: (e: any) => void
	// e: any because as it would otherwise overlap with existing types
	/**
	* requires experimental.newNextLinkBehavior
	*/
	onTouchStart?: (e: any) => void
	// e: any because as it would otherwise overlap with existing types
	/**
	* requires experimental.newNextLinkBehavior
	*/
	onClick?: (e: any) => void

Is there any context that might help us understand?

In Next.js 13, the new <Link> behavior was made default.

Does the docs page already exist? Please link to it.

No response

[balazsorban44]

Thanks, indeed the inline code documentation should reflect the new default behaviour. would you be interested in opening a PR?

[abayomi185]

I'm happy to open a PR for this.

[mkayander]

This issue can be now closed i suppose.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.