docs(eslint): clarify note for no-html-link-for-pages rule #83493
+3
−0
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 clarification that the rule
@next/next/no-html-link-for-pages
does not currently detect custompageExtensions
(e.g.,.mdx
,.page.tsx
).Linked to issue #53473 for reference.
For Contributors
Improving Documentation
pnpm prettier-fix
to fix formatting issues before opening the PR.What?
This PR updates the ESLint rules documentation by adding a clarification note for the rule
@next/next/no-html-link-for-pages
.The note explains that the rule does not currently detect pages when using custom
pageExtensions
(e.g.,.mdx
,.page.tsx
).Why?
Developers using custom
pageExtensions
may be confused when the rule does not apply to their setup.This clarification provides better guidance and links directly to the related issue.
How?
eslint.mdx
to include a blockquote note under the@next/next/no-html-link-for-pages
rule.Related
Fixes #53473