REL1CX

@JounQin I'll start working on this tomorrow.

I personally would like to have these two rules. The first rule was previously proposed in https://github.com/Rel1cx/eslint-react/pull/486 with a different name. However, under the premise of not compromising the plugin's...

In 2.0, I may consider adding back support for `React.createElement()` to the related rules, including this one, which means that these rules will not only detect JSX markup, but `React.createElement()`...

Sorry for the late reply to those who are following this rule. The development of this rule will be carried out ~~after the completion of [`react-x/no-unnecessary-use-effect`](https://github.com/Rel1cx/eslint-react/issues/1114)~~.

Update: The RC version of `eslint-plugin-react-hooks` introduces a new rule from the React team, `set-state-in-effect`, which validates against calling `setState` synchronously within an effect (see [React Docs](https://react.dev/reference/eslint-plugin-react-hooks/lints/set-state-in-effect)) In codebases that...

https://github.com/johnsoncodehk/tsslint/issues/41 TSSLint had the same issue before and they solved it. It seems we can refer to their solution https://github.com/johnsoncodehk/tsslint/commit/9b1e0f47698ef560bd35b927e0b3cc5faafb6eee.

@overlookmotel Thanks for reaching out, and that's an good question. The confusion is completely understandable because of how ESLint's configuration and rule parsing have evolved. Let me address your points...

So, the config file as shown below is closer to ESLint’s current behavior: ```json { "jsPlugins": [ "@eslint-react", "@eslint-react/dom", "@eslint-react/naming-convention" ], "rules": { "@eslint-react/jsx-no-comment-textnodes": ["error"], "@eslint-react/dom/no-dangerously-set-innerhtml": ["error"], "@eslint-react/naming-convention/context-name": ["error"] }...

[@overlookmotel](https://github.com/overlookmotel) I have reorganized the reply in https://github.com/oxc-project/oxc/issues/14557#issuecomment-3399160211, and I hope it can better answer your questions this time.

This feature request has been accepted, I will add a `jsx-key-before-spread` rule.