import-js/eslint-plugin-import

Suggestion [`no-named-default`]: add option to allow type imports with multiple imports

Open

#1869 aperta il 5 ago 2020

Vedi su GitHub
 (6 commenti) (4 reazioni) (0 assegnatari)JavaScript (1540 fork)batch import
bughelp wantedtypescript

Metriche repository

Star
 (4946 star)
Metriche merge PR
 (Merge medio 5g 21h) (9 PR mergiate in 30 g)

Descrizione

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

Guida contributor