Skip to content

Switch from eslint-plugin-jsx-expressions to @eslint-react/no-leaked-conditional-rendering #413

@karlhorky

Description

@karlhorky

Since eslint-plugin-jsx-expressions is not being maintained as much and doesn't support ESLint v9, switch eslint-plugin-jsx-expressions to the @eslint-react/no-leaked-conditional-rendering rule

Then the vendor directory can be removed

And eslint-config-upleveled can be added to the "Who is Using" list:

Show original issue

Title: Consider switching from eslint-plugin-jsx-expressions to @typescript-eslint/strict-boolean-expressions

Since eslint-plugin-jsx-expressions is not being maintained as much and doesn't support ESLint v9, consider switching from eslint-plugin-jsx-expressions to @typescript-eslint/strict-boolean-expressions

Then the vendor directory can be removed

Could be a downside for students though, since it will be reported also on if conditions

typescript-eslint Playground

Screenshot 2024-08-17 at 13 59 42

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions