import-js/eslint-plugin-import
Auf GitHub ansehenSuggestion [`no-named-default`]: add option to allow type imports with multiple imports
Open
#1.869 geöffnet am 5. Aug. 2020
bughelp wantedtypescript
Repository-Metriken
- Stars
- (4.946 Stars)
- PR-Merge-Metriken
- (Durchschn. Merge 5T 21h) (9 gemergte PRs in 30 T)
Beschreibung
Typescript's import type cannot be used to import the default export and named exports without using default as:
import type Foo, {Bar} from 'foo'
// A type-only import can specify a default import or named bindings, but not both.
However, these both work but trigger no-duplicates and no-named-default respectively:
import type Foo from 'foo'
import type {Bar} from 'foo'
import type {default as Foo, Bar} from 'foo'
Could there be a new option to no-named-default that allows type imports with multiple imports? For example:
import type {default as Foo} from 'foo' // lint warning
import type {default as Foo, Bar} from 'foo' // fine