Mixed `type` imports does not trigger `import/no-duplicates`

描述

import { useEffect } from "react";
import { useState } from "react";

import { type ComponentProps, useEffect } from "react";
import { useState } from "react";

import { type ComponentProps, useEffect, useState } from "react";

贡献者指南

技术栈

javascripttypescript

领域

toolingdeveloper experience

议题类型

bug

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

half day

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

fresh

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

Basic ESLint plugin knowledgeUnderstanding of TypeScript type imports

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

75

研究方向

Investigate the `import/no duplicates` rule implementation in the repository, likely in `src/rules/no duplicates.js`. Understand how imports are currently parsed and duplicates detected. The fix should treat mixed type and value imports from the same module as duplicates. Look at existing tests to understand the expected behavior and add a test case for mixed imports. Review any related comments in the issue for additional context.