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

Repository metrics

Stars

15,497 stars (15,497 stars)

PR merge metrics

Avg merge 12h 56m (Avg merge 12h 56m)52 merged PRs in 30d (52 merged PRs in 30d)

Description

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;

Contributor guide

Research direction

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.

Tech stack

typescriptnodejs

Domain

cli

Issue type

Bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

TypeScript knowledgecommitlint configuration concept

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

65