Apply consistent-type-specifier only for detecting type or interface #10281
Replies: 1 comment
-
There's no rule named
It looks like you're going for one or both of either:
For the former, For the latter, you can file a new issue: ✨ New Rule Option or Additional Check. Be sure to search for existing issues to make sure you're not filing a duplicate.
This discussion was filed under the "Technical Discussions: Deeper questions about typescript-eslint's architecture and/or APIs" category... but this is not a deep question about architecture or APIs. Request: please read the contributing guidelines more deeply before posting. They're there for a reason - to help you work with the systems we've set up for good reason. 🙂 Closing this discussion as non-actionable. Thanks for filing! |
Beta Was this translation helpful? Give feedback.
-
Body
Hello guys,
I have observed that consistent-type-specifier declare my class component as a type in the import declaration:
I expected to have:
I think that when we declare:
import type AType from "./Abc"
we are sure that AType is a type or interface exported declaration.
I feel weird to see:
"import type AClass from "./Abc"
and see that AClass is a class component instead of a type or an interface.
That is the reason I am asking if there is an option that we can add in order to use consistent-type-specifier and only apply the changes for a type or an interface exported component.
Thanks in advance for your response.
Additional Info
Any additional info...
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