[no-duplicates] prefer-inline should merge type and non-type imports

描述

import { A } from "./mod";
import type { B } from "./mod";

import { A, type B } from "./mod";

貢獻者指南

技術棧

javascripttypescriptnodejs

領域

developer experiencetooling

議題類型

feature

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

3

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

half day

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

fresh

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

basic knowledge of ESLint plugin structureunderstanding of TypeScript import syntax

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

70

研究方向

Investigate the current implementation of the `prefer inline` rule in `src/rules/prefer inline.js`. The issue specifies that consecutive import statements from the same module (one type only, one value) should be merged into a single import with the `type` keyword used inline. Look at how the rule currently handles import declarations and identify where to add logic to detect and merge such imports. Check if there are existing tests in `tests/src/rules/prefer inline.js` and consider adding test cases for this scenario. The fix should only apply when the imports are side by side and from the same module.