sindresorhus/eslint-plugin-unicorn

Enforce error message style

Open

#26 建立於 2016年5月16日

在 GitHub 查看
 (8 留言) (0 反應) (0 負責人)JavaScript (5,022 star) (468 fork)user submission
enhancementhelp wanted

描述

https://github.com/sindresorhus/ava/pull/835#discussion_r63331538

I want to say: This is a failure, you should use a blimp

Which of the following should it be:

  • This is a failure, you should use a blimp
  • This is a failure. You should use a blimp
  • This is a failure. You should use a blimp.

Keep in mind that if we go for the last one, which looks the best, it becomes inconsistent with one sentence error messages, which usually don't end in a dot.

貢獻者指南

技術棧
javascript
領域
developer experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
unclear
前置要求
ESLint plugin development
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
The issue discusses deciding on a consistent style for error messages in ESLint plugin unicorn. Currently, there is no decided format; the community is debating between different punctuations. To resolve, review the discussion and linked PR #835 for context, then propose and implement an ESLint rule that enforces the chosen style across all error messages in the codebase.