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