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

P5-02: Improve tidy behavior after manual drag to preserve readable topology #25

New Issue
Closed
opened 2026-02-19 13:41:29 -05:00 by Rbanh · 1 comment
Rbanh commented 2026-02-19 13:41:29 -05:00
Owner
Copy Link

Objective

Make auto tidy robust after arbitrary manual moves without creating confusing reroutes.

Scope

  • Tune post-drag placement normalization and lane anchoring.
  • Reduce detour spikes after drag operations.
  • Ensure tidy keeps related functional groups visually coherent.

Acceptance Criteria

  • Dragging a major component then auto-tidy yields readable grouping.
  • Crossings/overlaps remain near-zero.
  • Detour ratio after tidy does not exceed agreed threshold on sample fixtures.
## Objective Make auto tidy robust after arbitrary manual moves without creating confusing reroutes. ## Scope - Tune post-drag placement normalization and lane anchoring. - Reduce detour spikes after drag operations. - Ensure tidy keeps related functional groups visually coherent. ## Acceptance Criteria - Dragging a major component then auto-tidy yields readable grouping. - Crossings/overlaps remain near-zero. - Detour ratio after tidy does not exceed agreed threshold on sample fixtures.
Rbanh added this to the Phase 5 - Layout Robustness and JSON Import UX Hardening milestone 2026-02-19 13:41:56 -05:00
Rbanh commented 2026-02-19 14:00:41 -05:00
Author
Owner
Copy Link

Delivered in commit 8b6c959.

What shipped:

  • Added explicit drag-then-auto-tidy quality checks in tests/ui-regression-runner.js.
  • Enforced post-drag tidy budgets for crossings/overlaps/detour via env-configurable thresholds.
  • Captured after_drag_tidy metrics in the UI report artifact.

Verification:

  • Drag -> tidy path now gated in CI through npm run test:ui.
  • Current report: 0 crossings, 0 overlaps, detour within threshold.
Delivered in commit `8b6c959`. What shipped: - Added explicit drag-then-auto-tidy quality checks in `tests/ui-regression-runner.js`. - Enforced post-drag tidy budgets for crossings/overlaps/detour via env-configurable thresholds. - Captured `after_drag_tidy` metrics in the UI report artifact. Verification: - Drag -> tidy path now gated in CI through `npm run test:ui`. - Current report: `0 crossings`, `0 overlaps`, detour within threshold.
Rbanh closed this issue 2026-02-19 14:00:50 -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 5 - Layout Robustness and JSON Import UX Hardening
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#25
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?