tscircuit / tscircuit/schematic-trace-solver
JSON Bug Report:
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 314
- Avg merge
- 9h 3m
- Merged PRs (30d)
- 132
Description
Solver input JSON attachment
_board#97 _-SchematicTracePipelineSolver-solver-input.json
Notes
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the attached _board#97 _-SchematicTracePipelineSolver-solver-input.json file and determine what solver behavior is incorrect. The issue does not identify an expected result, failing entry point, or test, so clarify the reproduction and acceptance criteria before choosing files to change. Done should mean the reported JSON input produces the expected routing result with a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100