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

(6 评论) (4 反应) (0 负责人)JavaScript (4,946 star) (1,540 fork)batch import

bughelp wantedtypescript

描述

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

技术栈: typescriptjavascript
领域: developer experiencetooling
议题类型: feature
难度: 3
预计时间: 1-2 days
活动状态: stale
清晰度: clear
前置要求: TypeScriptESLint plugin development basics
新手友好度: 45
研究方向: 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.