Should @typescript-eslint/no-use-before-define be removed in favour of native no-use-before-define
#11794
Closed
ipanasenko
started this conversation in
Technical Discussions
Replies: 1 comment
-
|
See #11014 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Body
Hi!
I've noticed that native
no-use-before-definesupports all the same options as@typescript-eslint/no-use-before-define(+ additionalnofuncoption).Does it still make sense to use
@typescript-eslint/no-use-before-defineinstead of nativeno-use-before-definerule?Additional Info
Links:
https://typescript-eslint.io/rules/no-use-before-define/
https://eslint.org/docs/latest/rules/no-use-before-define#options
Before you submit your discussion, please confirm the following. If any of these required steps are not taken, we may not be able to review your RFC. Help us to help you!
Beta Was this translation helpful? Give feedback.
All reactions