-
Notifications
You must be signed in to change notification settings - Fork 24.3k
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-native-community/eslint and TypeScript 3.7 #27690
Comments
Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety? 👉 Click here if you want to take another look at the Bug Report issue template. |
+1 |
1 similar comment
+1 |
There is an open PR that could resolve the issue once merged. |
the community eslint config has updated prettier to v2 in this commit 89d04b5#diff-07d8dac5e415f4617208ba79d55bc35f which should resolve the issue |
I believe this issue is resolved, as |
Have just tested it with 1.1.0 doesn't seem to work (at least for me) |
Now my only problem is that it ignores our |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
react-native-community/eslint
useswhich are limited to TypeScript
3.5.*
, blocking features likenull coalescing
andoptional chaining
. With the overrides below I managed to skip such errors and get only the errors I really had to deal with.I can create a PR fixing it if you guys want
React Native version:
Steps To Reproduce
TypeScript 3.7
andreact-native-community/eslint:0.0.6
The text was updated successfully, but these errors were encountered: