-
-
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
prefer-default-export
fails on Typescript type declaration
#1332
Labels
Comments
Not sure if this helps or not, but this was addressed once a while back: #639 seems like this bug was reintroduced. |
That was for flow, this is for typescript. |
and if I'm not mistaken, both export type insert_type_name_here syntax, so unless the parser was explicitly looking for |
👋 are there any news on this? |
ljharb
pushed a commit
to sharmilajesupaul/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
…tion or type alias. Fixes import-js#1332.
ljharb
pushed a commit
to sharmilajesupaul/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
…tion or type alias. Fixes import-js#1332.
ljharb
pushed a commit
to sharmilajesupaul/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
…tion or type alias. Fixes import-js#1332.
sharmilajesupaul
added a commit
to sharmilajesupaul/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
sharmilajesupaul
added a commit
to sharmilajesupaul/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
sharmilajesupaul
added a commit
to sharmilajesupaul/eslint-plugin-import
that referenced
this issue
Jul 17, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
import/prefer-default-export
erroneously warns on files that contain a single exported type.eg:
Related issue: #1164
The text was updated successfully, but these errors were encountered: