fix: <title> type-enum inside RuleConfigSeverity.Error is not working.

倉庫指標

星標

15,497 顆星 (15,497 顆星)

PR 合併指標

平均合併 12小時 56分鐘 (平均合併 12小時 56分鐘)30 天內合併 52 個 PR (30 天內合併 52 個 PR)

描述

import { RuleConfigSeverity, UserConfig } from '@commitlint/types';

const Configuration: UserConfig = {
   rules: {
		"type-enum": [
			RuleConfigSeverity.Error,
			"always",
			[
				// Changes related to the build process or build tools.
				"build",
				// Changes that introduce functional or behavioral modifications.
				"change",

				// Miscellaneous tasks or maintenance chores that don't affect functionality.
				"chore",
                  ]
}

export default Configuration;

貢獻者指南

研究方向

Examine the `@commitlint/types` package to understand how `RuleConfigSeverity` is defined. Look at the `type enum` rule implementation in `@commitlint/rules` to see how it processes severity values. The issue may be that `RuleConfigSeverity.Error` is not being correctly imported or not properly parsed as a numeric value. Test with the provided configuration and ensure the rule correctly interprets the enum member.

技術棧

typescriptnodejs

領域

cli

議題類型

錯誤

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

3

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

1-3 小時

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

活躍

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

清晰

前置要求

TypeScript knowledgecommitlint configuration concept

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

65