Suggestion [`no-named-default`]: add option to allow type imports with multiple imports · import-js/eslint-plugin-import#1869

(6 comments) (4 reactions) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import

bughelp wantedtypescript

Description

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

Tech stack: typescriptjavascript
Domain: developer experiencetooling
Issue type: feature
Difficulty: 3
Estimated time: 1-2 days
Activity status: stale
Clarity: clear
Prerequisites: TypeScriptESLint plugin development basics
Newbie friendliness: 45
Research direction: The issue requests a new option for the `no named default` rule to allow type imports with multiple imports. Examine the rule's source code in the repository, likely at `src/rules/no named default.js`. Understand how the rule currently processes imports and identify where to add logic for `import type` statements. Update the rule's documentation and add tests for the new option. Look at linked discussions in the issue comments for further clarifications.