feat: add "ignoreTypeDefault" option to "type-import-style" #393
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.
The newly added
ignoreTypeDefault
option, lets you avoid cases where therule would normally complain for
import type foo from "...";
when in"identifier" mode. This is desirable because
import {type default as foo} from '...';
is kinda long, when you wouldotherwise prefer
import type foo from '...';
. Also,type default as foo
conflicts with
eslint-plugin-import
'simport/no-named-default
https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-named-default.md