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.