sindresorhus/eslint-plugin-unicorn

Rule proposal: opposite of `prefer-string-raw`

Open

#2,652 建立於 2025年5月11日

在 GitHub 查看
 (1 留言) (2 反應) (0 負責人)JavaScript (5,022 star) (468 fork)user submission
help wantednew rule

描述

Description

During refactoring, some strings may not need String.raw anymore, should use a string literal instead.

Examples

// ❌
String.raw`a`

// ✅
'a'

Proposed rule name

no-string-raw

Additional Info

Not sure if we want to add a separate rule, or just add to prefer-string-raw.

貢獻者指南

技術棧
javascriptnodejs
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
ESLint plugin developmentAST concepts
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
This issue proposes a new rule 'no string raw' to disallow unnecessary use of String.raw. The maintainer suggested possibly extending the existing 'prefer string raw' rule. A contributor should investigate the current implementation of 'prefer string raw' in the repository to see if it can be easily extended or if a new rule is preferred. The contributor should open a discussion or draft PR to clarify the scope. The relevant files are likely in the rules/ directory of the eslint plugin unicorn repo.