-
-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
react/jsx-no-undef consistency #3319
Comments
I try also to use https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-no-undef.md to define the eslintrc.json but nothing. |
Thank you for the feedback, I'll update the rule with these options. https://github.com/jsx-eslint/eslint-plugin-react/blob/master/docs/rules/jsx-no-undef.md#rule-options |
Many thanks, I really like the project and simplify alot of things! Thanks. |
In the next version: In your {
"globals": {
"dispatcher": "readonly"
}
} |
Hello, recently I move from ESlint to OXC. I figured out an issue about "react/jsx-no-undef" that not record the "0" or "off" or false
I need to stop the warning.
I have a global function (please, don't ask...) and previously works fine.... also "elem"
In substance any globals created into the project going to give me a warning is used as components.
Error:
"eslint-plugin-react(jsx-no-undef): Disallow undeclared variables in JSX
help: 'dispatch' is not defined. oxc"
I try to fix via the .d.ts but not lucky here!
Many thanks.
Dario Passariello
The text was updated successfully, but these errors were encountered: