-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[New] no-unused-modules
: consider exported TypeScript interfaces, types and enums
#1819
Merged
ljharb
merged 1 commit into
import-js:master
from
nicolashenry:feature/consider-interfaces-types-enums
Jun 11, 2020
Merged
[New] no-unused-modules
: consider exported TypeScript interfaces, types and enums
#1819
ljharb
merged 1 commit into
import-js:master
from
nicolashenry:feature/consider-interfaces-types-enums
Jun 11, 2020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ypes and enums Fixes import-js#1680 Co-authored-by: e020873 <nicolas.henry-partner@arcelormittal.com> Co-authored-by: Jordan Harband <ljharb@gmail.com>
3 similar comments
ljharb
force-pushed
the
feature/consider-interfaces-types-enums
branch
from
June 11, 2020 23:01
98ea37e
to
f064772
Compare
ljharb
approved these changes
Jun 11, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I added in a minor refactor to avoid duplication.
ljharb
changed the title
consider exported TypeScript interfaces, types and enums
[Fix] Jun 11, 2020
no-unused-modules
: consider exported TypeScript interfaces, types and enums
ljharb
changed the title
[Fix]
[New] Jun 11, 2020
no-unused-modules
: consider exported TypeScript interfaces, types and enumsno-unused-modules
: consider exported TypeScript interfaces, types and enums
ljharb
force-pushed
the
feature/consider-interfaces-types-enums
branch
from
June 11, 2020 23:04
f064772
to
54eb51b
Compare
This was referenced Mar 18, 2021
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1680
Note that
babel-eslint
parser does not handle typescript enums and do not produce the same declaration types as@typescript-eslint/parser
.babel-eslint
=>InterfaceDeclaration
,TypeAlias
@typescript-eslint/parser
=>TSInterfaceDeclaration
,TSTypeAliasDeclaration
,TSEnumDeclaration