`parserPreset` in `.commitlintc.json` is ignored · conventional-changelog/commitlint

(4 件のコメント) (0 件のリアクション) (0 人の担当者)TypeScript (896 件のフォーク)batch import

bughelp wanted

Repository metrics

Stars: (15,497 個のスター)
PR merge metrics: (平均マージ 12h 56m) (30d で 52 merged PRs)

説明

Steps to Reproduce

Create .commitlintrc.json with the following contents

{
  "extends": ["@commitlint/config-conventional"],
  "parserPreset:": {
    "parserOpts": {
      "issuePrefixes": ["PREFIX-"]
    }
  },
  "rules": {
    "references-empty": [2, "never"]
  }
}

Run echo "feat: some feature (PREFIX-123)" | npx commitlint and observe how an error for empty references is thrown.
Run npx commitlint --print-config and observe how parserPreset.parserOpts.issuePrefixes is [ '#' ].

With a commitlint.config.js this does not happen.

Current Behavior

see above.

Expected Behavior

It should correctly pick up parserPreset from the JSON configuration.

Affected packages

cli
core
prompt
config-angular

Possible Solution

No response

Context

No response

commitlint --version

@commitlint/cli@19.3.0

git --version

2.45.2

node --version

v20.13.1

コントリビューターガイド

調査方針: The issue likely lies in the configuration loading logic, specifically how `loadConfig` handles JSON vs JS files. Investigate the `@commitlint/load` package, focusing on the `parserPreset` key handling. Look at the source files like `src/load.ts` or similar. Check how the config is parsed and if there is a difference in the way `parserPreset` is applied for JSON configs. Possible fix involves ensuring that `parserPreset` from JSON config is recognized and merged similarly to JS config.
技術スタック: typescriptjavascriptnodejs
領域: cli
Issue 種別: バグ
難度: 3
推定時間: 1-3時間
活動状況: 新着
明確さ: 明確
前提条件: Node.jsTypeScriptcommitlint configuration
初心者向け度: 70