import-js/eslint-plugin-import

[import/extensions] ".." and "." import paths are incorrectly flagged as requiring an extension, when either is al local package

Open

#2,844 建立於 2023年7月31日

在 GitHub 查看
 (2 留言) (2 反應) (0 負責人)JavaScript (4,946 star) (1,540 fork)batch import
bughelp wanted

描述

In #2778, we determined that this plugin incorrectly flags ".." and "." import paths, when those imports refer to a local package (with a package.json).

貢獻者指南

技術棧
javascriptnodejs
領域
toolingdeveloper experience
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
needs maintainer response
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of ESLint custom rulesNode.js module resolution
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue references #2778 where a similar case was discussed. To fix, examine the `import/extensions` rule implementation in the plugin, likely in `src/rules/extensions.js` or similar. Investigate how the rule determines whether a path is a local package by checking for a `package.json` in the directory. The fix should ensure that relative paths like '.' and '..' that resolve to a package (with a `package.json`) are not flagged as requiring an extension. Test cases should be added for this scenario.
[import/extensions] ".." and "." import paths are incorrectly flagged as requiring an extension, when either is al local package · import-js/eslint-plugin-import#2844 | Good First Issue