[repo-assist:issue-triage] githubnext/gh-cao issue 20097 triage guidance

Open
  • Is something wrong?
#20,103 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
15/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
documentation, frontend

Research direction

Start with the aicc branch of formatNumber in dashboard/site/src/view-formatters.js, which calls formatAicc after rounding to 2 significant figures. Then read DLS-UNIT-004 in docs/dashboard-language-specification.md, since the spec mandates that rounding and a maintainer must approve any change before code is touched. Done means 39 AIC renders $0.39, the formatter tests and significant: 2 fixtures are updated, and the dashboard test suite passes.

Written by the indexing model from the issue text.

Description

repo-assist repo-assist:issue-triage

Target githubnext/gh-cao issue 20097 (Cost page AIC rounding): the behavior is real but spec-mandated, so a fix needs a maintainer decision on DLS-UNIT-004 first. Confidence: high.

Action: A dashboard maintainer should decide whether to amend DLS-UNIT-004 (cents-grain rounding); if approved, assign the issue to Copilot with the prompt below. Acceptance: 39 AIC renders $0.39, 117 AIC renders $1.17, and dashboard unit tests and npm run check pass.

Evidence
  • docs/dashboard-language-specification.md DLS-UNIT-004 requires an aicc presenter to round the AIC value to significant: 2 before dividing by 100. 39 AIC becomes 40 and renders $0.40, matching the report.
  • dashboard/site/src/view-formatters.js formatNumber calls formatAicc(rounded) for aicc units, which implements that rule. It is not an implementation bug.
  • Rounding to 2 AIC gives $0.02 granularity, so sums of displayed parts cannot reconcile with totals. Rounding after the divide by 100 (cents) fixes this.
  • Rejected: tooltip-only unrounded AIC. It leaves the visible figures inconsistent.
  • Breaking-spec risk: changing a MUST rule requires updating the spec, docs/, formatter tests and contract fixtures together.
Agent prompt

In githubnext/gh-cao, change aicc formatting so the AIC value is divided by 100 and then rounded to cents, instead of being rounded to 2 AIC first. Update formatNumber in dashboard/site/src/view-formatters.js, amend DLS-UNIT-004 in docs/dashboard-language-specification.md, and update any significant: 2 fixtures or tests. Add a unit test showing 39 AIC renders $0.39 and three of them sum to $1.17. Run npm test, npm run lint and npm run typecheck in dashboard/site/, then npm run docs:build.

Control Plane

cao: githubnext/gh-cao, correlation: 41444087799-128

Generated by 🏷️ Repo Assist / Issue Triage · copilot · auto · ~20 AIC · ⌖ ~1 AIC · ⊞ 14K · ◷

  • expires on Nov 16, 2026, 12:32 PM UTC
Dominant language
JavaScript
Stars
14
Forks
5
Avg merge
3h 20m
Merged PRs (30d)
811

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-cao

All issues in githubnext/gh-cao

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.