badges/shields

Enhance TeamCity Coverage Badge

Open

#3,111 建立於 2019年2月27日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)JavaScript (22,337 star) (5,423 fork)batch import
good first issueservice-badge

描述

:clipboard: Description

Enhance the TeamCity Coverage Badge to allow the user to specify the coverage metric (lines, statements, etc.) they want to use via a param.

Our current badge implementation is keying off statement coverage, but while I was working on resolving https://github.com/badges/shields/issues/2901 I noticed that a lot (actually the majority) of TeamCity projects with coverage did not have statement coverage (most had line coverage long with method/function, and others).

If we allowed the user to specify their target coverage metric (we can still default to statement) then we can make the coverage badge for TeamCity available to a much broader set of users

貢獻者指南

技術棧
javascriptnodejs
領域
developer experience
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Node.js experienceShields codebase familiarity
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
70
研究方向
Examine the existing TeamCity coverage badge implementation in the Shields codebase. Identify where the coverage metric is currently hardcoded to 'statement'. Add support for a query parameter (e.g., `metric`) that allows users to specify 'line', 'statement', etc., defaulting to 'statement'. Refer to linked issue #2901 for context on how other coverage badges handle this.