eslint-plugin-react

eslint-plugin-react copied to clipboard

Feature request: abortController + no-leaked-event-listener

3

i've been using this pattern to clean up event listeners lately: ```typescript useEffect(() => { const abortController = new AbortController(); const { signal } = abortController; window.addEventListener( "click", (event) =>...

andybarron

[Bug]: react/jsx-sort-props is not able to sort if there is comment between properties and reported as ESLintCircularFixesWarning in ESlint 9

1

### Is there an existing issue for this? - [x] I have searched the existing issues, and my issue is unique - [x] My issue appears in the command-line and...

webmatrixxxl

[New] `jsx-sort-props`: add `sortFirst` option to explicitly specify prop names to sort first

5

Fixes: #3175 #3639 #3193 > [!WARNING] > I had to pin the ESLint version in the published types test project, as the ESLint types break with TypeScript 4.0 starting with...

loderunner

[fix] `no-unknown-property` - add onScrollEnd and onScrollEndCapture events as known properties

2

This includes onScrollEnd and onScrollEnd capture as recognized elements. While creating #3957 I realized i could just fix it.

xfeeefeee

Update configs format for use with defineConfig()

11

The format for flat configs in `eslint-plugin-react` is outside the norm for ESLint plugins. Currently: ```js const react = require('eslint-plugin-react'); module.exports = [ react.configs.flat.recommended ]; ``` What I'd like to...

nzakas

### Is there an existing issue for this? - [x] I have searched the existing issues and my issue is unique - [ ] My issue appears in the command-line...

VandinVanadium

I came across this today and thought I might as well try and fix it. The following wasn't triggering a warning, even though it should ( ? ) ``` function...

holoflash

### Is there an existing issue for this? - [x] I have searched the existing issues and my issue is unique - [x] My issue appears in the command-line and...

xfeeefeee

Fixes #3524 This PR fixes a bug where `react/no-unused-prop-types` was not properly detecting unused props in components wrapped with nested wrapper functions like `React.memo(React.forwardRef())`. - Enhanced component detection logic to...

avaice

This PR fixes the problem where the `jsx-handler-names` rule with `ignoreComponentNames` option throws an error when it checks an component that is namespaced like ``. Fixes #3954.

takuji