Skip to content
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

Why doesn't this config disable eslint/no-use-before-defined? #35

Closed
FunctionDJ opened this issue Apr 13, 2021 · 1 comment
Closed

Why doesn't this config disable eslint/no-use-before-defined? #35

FunctionDJ opened this issue Apr 13, 2021 · 1 comment

Comments

@FunctionDJ
Copy link

Leaving this rule enabled in for example .tsx files causes this error:
'React' was used before it was defined.

Typically this is resolved by using replacing this rule with @typescript-eslint/no-use-before-define as can be seen here.

Why does this config not do that? I was kinda bummed because i thought i could use xo with my TypeScript + React project out of the box ^^'

@FunctionDJ FunctionDJ changed the title Why doesn't this config disable eslint/no-use-before-undefined? Why doesn't this config disable eslint/no-use-before-defined? Apr 13, 2021
@FunctionDJ
Copy link
Author

Nevermind, i'm stupid. This the VSCode ESLint plugin still hanging around, even though i removed the config. Reloading VSCode fixed this. Sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant