import-js/eslint-plugin-import

[no-restricted-paths] Add options to ignore type imports

Open

#1,899 建立於 2020年9月14日

在 GitHub 查看
 (7 留言) (9 反應) (0 負責人)JavaScript (4,946 star) (1,540 fork)batch import
enhancementhelp wantedtypescript

描述

Can an option be added to the no-restricted-paths rule to ignore TypeScript's type imports?

// Allow this.
import type { T } from 'some/restricted/path';

// While still disallowing this.
import { foo } from 'some/restricted/path';

My proposal is to add an option at the top level of the config called something along the lines of allowedImportKinds which can be set to any number of the following options: "type" or "value". Additionally, this option could be available in each "zone" so that individual zones can override this behavior (but this may not be needed).

I haven't touched this project's code base before but I can probably whip up a PR for this.

貢獻者指南

技術棧
javascripttypescript
領域
developer experiencetooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
ESLint plugin basicsTypeScript import syntax
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Investigate the no restricted paths rule implementation in the eslint plugin import repository, specifically how options are defined and validated. Look at existing tests to understand the expected behavior. Consider how to add an `allowedImportKinds` option that filters type imports from the restriction. Also review any existing configuration patterns in the plugin.
[no-restricted-paths] Add options to ignore type imports · import-js/eslint-plugin-import#1899 | Good First Issue