Rbanh/schemeta
1
0
Fork 0
Code Issues 11 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Normalize compile status metrics across compile/layout actions #10

New Issue
Closed
opened 2026-02-18 21:33:30 -05:00 by Rbanh · 1 comment
Rbanh commented 2026-02-18 21:33:30 -05:00
Owner
Copy Link

Objective

Unify status line metric reporting so compile and layout actions show the same metric set and formatting.

Context

Live browser testing found inconsistency: normal compile path shows detour metric while layout action path differs.

Scope

  • Refactor status string generation into a shared formatter.
  • Ensure all compile entry points use the same metric fields.
  • Keep deterministic ordering and compact readability.

Acceptance Criteria

  • Status line is identical in structure for compile, auto-layout, and auto-tidy results.
  • Includes consistent metric set (crossings, overlaps, bends, tie-nets, detour).
  • No regressions in existing tests.
## Objective Unify status line metric reporting so compile and layout actions show the same metric set and formatting. ## Context Live browser testing found inconsistency: normal compile path shows detour metric while layout action path differs. ## Scope - Refactor status string generation into a shared formatter. - Ensure all compile entry points use the same metric fields. - Keep deterministic ordering and compact readability. ## Acceptance Criteria - Status line is identical in structure for compile, auto-layout, and auto-tidy results. - Includes consistent metric set (`crossings`, `overlaps`, `bends`, `tie-nets`, `detour`). - No regressions in existing tests.
Rbanh added this to the Phase 3 - Browser QA and UX Consistency milestone 2026-02-18 21:33:51 -05:00
Rbanh commented 2026-02-18 21:44:52 -05:00
Author
Owner
Copy Link

Completed in commit d5836a2.

Delivered:

  • Added shared compile status formatter to normalize reporting across compile, auto-layout, and auto-tidy paths.
  • Standardized metric ordering/format: crossings, overlaps, bends, tie-nets, detour.
  • Verified via automated tests and browser regression flow.

Validation:

  • npm test
  • npm run test:ui
Completed in commit `d5836a2`. Delivered: - Added shared compile status formatter to normalize reporting across compile, auto-layout, and auto-tidy paths. - Standardized metric ordering/format: crossings, overlaps, bends, tie-nets, detour. - Verified via automated tests and browser regression flow. Validation: - `npm test` - `npm run test:ui`
Rbanh closed this issue 2026-02-18 21:44:59 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Phase 3 - Browser QA and UX Consistency
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Rbanh/schemeta#10
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?