Skip to content

fix(eslint-plugin): support pageExtensions config in no-html-link-for-pages rule#91056

Open
alvinttang wants to merge 1 commit intovercel:canaryfrom
alvinttang:fix/53473-pageextensions
Open

fix(eslint-plugin): support pageExtensions config in no-html-link-for-pages rule#91056
alvinttang wants to merge 1 commit intovercel:canaryfrom
alvinttang:fix/53473-pageextensions

Conversation

@alvinttang
Copy link

The no-html-link-for-pages rule was hardcoded to only detect .js, .jsx, .ts, and .tsx page extensions. This fix adds support for custom pageExtensions configured in ESLint settings.

Fixes #53473

…-pages rule

The no-html-link-for-pages rule was hardcoded to only detect .js, .jsx, .ts, and .tsx page extensions. This fix adds support for custom pageExtensions configured in ESLint settings.

Fixes vercel#53473
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: e5baf16

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

1 similar comment
@nextjs-bot
Copy link
Collaborator

Allow CI Workflow Run

  • approve CI run for commit: e5baf16

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@next/next/no-html-link-for-pages rule does not work with pageExtensions

3 participants