eslint-plugin-react

eslint-plugin-react copied to clipboard

[Bug]: jsx-handler-names crashes on compound components

2

### 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...

djankies

[Bug]: propElementValues option of react/jsx-curly-brace-presence doesn't catch JSX fragments as prop values

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...

mfigard

[Fix] catch JSX fragments with propElementValues

1

Bug report: #3951 This proposed fix treats JSX fragments like JSX elements when handling the `propElementValues` option: * It checks for unnecessary curly brackets in JSX fragments just like it...

mfigard

[New]: `jsx-no-literals`: add restrictedAttributes option

1

## Add `restrictedAttributes` option to `jsx-no-literals` rule ### Summary This PR introduces a new `restrictedAttributes` option for the `jsx-no-literals` rule. With this option, you can enforce translation (i18n) only for...

ushiboy

Hi team, I'm working on a JS-only codebase(no `.ts` or `.tsx` files), but we use TypeScript declaration(`.d.ts`) files to define types for our components. I've configured eslint with `eslint-plugin-react` to...

AbhinavRajesh

[Enhancement]: New option of jsx-no-bind to allow pass arguments

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...

woody-li

Enforce explicit return statements in arrow functions

3

I would like to propose a change to [`react/function-component-definition`](https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/function-component-definition.md) or a new adjacent rule. When a component is defined as an arrow function, we can choose to use a shorthand...

kachkaev

[New]: `forbid-dom-props`: support React Strict Dom elements (`html.div`, etc)

6

## Summary Add suport for [React Strict DOM](https://facebook.github.io/react-strict-dom/) notation of DOM nodes: `html.div`, `html.span`, `h.h1`, etc ## Details The code is based on `forbid-component-props` rule that already supported `Namespace.Component` notation....

mdjastrzebski

Add note about not needing jsx-no-undef with TS / typescript-eslint

1

Hi @ljharb, hope everything is going well! 👋 Quick PR to add an additional 2 cases of when to not use `react/jsx-no-undef` 1. when using TypeScript, since it has [better...

karlhorky

junaidkbr