conventional-changelog/commitlint

feat: parsable output format

Open

#4,457 建立於 2025年6月15日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)TypeScript (15,497 star) (896 fork)batch import
featurehelp wanted

描述

Expected Behavior

Commitlint prints line and column numbers where the issue was found, to allow parsing the output for IDE integration (for example vim with neomake), like all major linters do. This should be the default behaviour TBH.

Current Behavior

Commitlint cat-s the message and writes issues found without any context. Formatter doesn't support line and column fields.

Affected packages

  • cli
  • core
  • prompt
  • config-angular

Possible Solution

At least line and column fields should be available in the formatter API.

Context

No response

貢獻者指南

技術棧
typescriptnodejs
領域
clideveloper experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
TypeScript basicscommitlint formatter APINode.js CLI tools
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
Start by examining the formatter API in packages/format. Look at how messages are currently structured and where line/column information could be added. The issue suggests adding line and column fields to the formatter output. Check existing formatter implementations to see how they could be extended. Then propose a change to include line and column numbers in the output.