You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the improvement or update you wish to see?
I was reviewing the latest changes of next/link and noticed that the docs refer to a next/link-passhrefESLint rule, but I couldn't find its definition in the Next plugin. Was this rule removed? And if so, the docs should be updated.
Is there any context that might help us understand?
With the new changes introduced by Next 13, is important for the docs to be up to date!
Does the docs page already exist? Please link to it.
Yes, looks like it was removed. #36511
Although I don't think it should have been! In a few cases, we're using legacyBehavior which seems to still require passHref?
I've noticed this too. The documentation mentions this rule and I was confused as to why I couldn't trigger a linting error from this rule.
Does the documentation need updating or does this lint rule need bringing back and potentially updating?
In my debugging I got a config dump form eslint for the file I was editing and can see that there is no next/link-passhref rule listed in the generated rules section of the config being passed to eslint.
Does the documentation just need updating or does this lint rule need bringing back?
What is the improvement or update you wish to see?
I was reviewing the latest changes of
next/link
and noticed that the docs refer to anext/link-passhref
ESLint rule, but I couldn't find its definition in the Next plugin. Was this rule removed? And if so, the docs should be updated.Is there any context that might help us understand?
With the new changes introduced by Next 13, is important for the docs to be up to date!
Does the docs page already exist? Please link to it.
https://nextjs.org/docs/api-reference/next/link#if-the-child-is-a-custom-component-that-wraps-an-a-tag
The text was updated successfully, but these errors were encountered: