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
Relax rule: JSX: Consider the global scope when checking for defined Components (react/jsx-no-undef) #1115
Comments
This Important note seems related: https://github.com/vkbansal/eslint-plugin-jsx-control-statements#important |
Can this |
@DusanDimitric Yep, we can include this in the next release. |
Thanks ;) |
I'm going to leave this issue open so that I remember to include this in the next release. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I can see it's still giving an error here, can we please check this? |
I second this ^ |
Any update? :( |
Sorry for the delay – this will be fixed in |
Hi, I'm using
standard
withreact-native
andbabel-plugin-jsx-control-statements
.Standard version: v11.0.1
Problem
standard
shows errors forbabel-plugin-jsx-control-statements
globals such asIf
,Choose
etc. even though they're declared inpackage.json standard.globals
and thebabel-plugin-jsx-control-statements
is specified in.babelrc
(as seen below)Example output
Expected behavior
standard
should not throwreact/jsx-no-undef
errors for variables declared in package.json > standard.globals:I've seen this line in the CHANGELOG.md:
But I guess it doesn't relate to this case.
Let me know if I can provide any more details.
Thanks a lot,
D.D.
The text was updated successfully, but these errors were encountered: