Skip to content

fix(home): Current Coverage KPI shows too many decimal places, can overflow box #978

Closed

Description

@cristim

Bug report

QA row 557 — Home Page, step 1.1

Action: Load the Home page and observe the "Current Coverage" KPI tile.

Actual: The coverage value is rendered as a raw float (e.g. 72.3456789012%) with no decimal-place limit. At some screen resolutions this overflows the KPI tile box.

Expected: Coverage should be rounded to a fixed precision (1 decimal place, matching the formatting used for coverage percentages throughout the app, e.g. 72.3%).

Note: Only display formatting is affected; the underlying data value must not be changed. Sibling percentages in inventory.ts use .toFixed(1) — the Home KPI should match.

Activity

  1. added
    pr-createdA PR has been opened for this issue (dedup guard for the auto-PR loop)
    pr-mergedThe PR for this issue has been merged
    on Jun 7, 2026
  2. cristim commented on Jun 8, 2026

    @cristim
    MemberAuthor

    Closing as completed: the Current Coverage KPI one-decimal rounding fix shipped via #967 (commit 92db4e7) on base. Verified.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    impact/fewLimited audiencepr-createdA PR has been opened for this issue (dedup guard for the auto-PR loop)pr-mergedThe PR for this issue has been mergedpriority/p3Polish / idea / may never shipseverity/lowMinor harmtriagedItem has been triagedtype/bugDefecturgency/this-quarterWithin the quarter

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions