Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
2 of 4 tasks
yagnikvadi2003 opened this issue Aug 10, 2024 · 4 comments
Open
2 of 4 tasks

Comments

@yagnikvadi2003
Copy link

Steps to Reproduce

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;

Current Behavior

Screenshot from 2024-08-10 18-57-26

Expected Behavior

Screenshot from 2024-08-10 18-58-13

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Possible Solution

No response

Context

No response

commitlint --version

@commitlint/[email protected]

git --version

v2.46.0

node --version

v20.16.0

@knocte
Copy link
Contributor

knocte commented Aug 31, 2024

@yagnikvadi2003 hey, in your section "Steps to reproduce" I don't see any steps, I only see your config. Can you please be explicit about how you are reproducing the bug please?

@knocte
Copy link
Contributor

knocte commented Aug 31, 2024

BTW, your config file looks like it's missing a closing curly brace?

@yagnikvadi2003
Copy link
Author

Now Done process. Console cache problem.

@knocte
Copy link
Contributor

knocte commented Aug 31, 2024

Now Done process. Console cache problem.

I'm unable to understand what you mean with this text above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants