Skip to content

Introduce Ratsnest-Free Schematic Solver Visualizations for Cleaner Bug Report Snapshots#646

Open
AnasSarkiz wants to merge 2 commits into
tscircuit:mainfrom
AnasSarkiz:main
Open

Introduce Ratsnest-Free Schematic Solver Visualizations for Cleaner Bug Report Snapshots#646
AnasSarkiz wants to merge 2 commits into
tscircuit:mainfrom
AnasSarkiz:main

Conversation

@AnasSarkiz

Copy link
Copy Markdown
Member

Summary

Adds a hideRatsNet option to SchematicTracePipelineSolver so schematic debug visualizations can suppress unrouted ratsnest connection lines while preserving the existing default behavior.

Changes

  • Added hideRatsNet support to SchematicTracePipelineSolverParams.
  • Preserved backward compatibility by allowing the constructor to accept either an InputProblem directly or a params object.
  • Stores hideRatsNet on the solver and cloned input problem.
  • Updated visualizeInputProblem to skip direct/net connection ratsnest lines when enabled.
  • Ensures constructor params include hideRatsNet for solver replay/debug flows.
  • Updated bug-report snapshot tests to use cleaner ratsnest-free visualizations.

Impact

This makes schematic trace bug report snapshots easier to inspect by hiding noisy ratsnest overlays without changing routing behavior or solver output.

# Conflicts:
#	tests/bug-reports/bug-report-20260706T213649Z/__snapshots__/bug-report-20260706T213649Z.snap.svg
#	tests/bug-reports/bug-report-20260707T092615Z/__snapshots__/bug-report-20260707T092615Z.snap.svg
@vercel

vercel Bot commented Jul 8, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
schematic-trace-solver Ready Ready Preview, Comment Jul 8, 2026 2:05pm

Request Review

@MustafaMulla29 MustafaMulla29 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if modifying params in constructor is the right approach.

@MustafaMulla29 MustafaMulla29 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropping an approval, you should take review from seve/sangit as well

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants