Skip to content

repro: KiCad exports omit hierarchical child schematic files - #5218

Open
GokulPandi-M wants to merge 3 commits into
tscircuit:mainfrom
GokulPandi-M:repro-kicad-keepout-internal-pad
Open

GokulPandi-M wants to merge 3 commits into
tscircuit:mainfrom
GokulPandi-M:repro-kicad-keepout-internal-pad

Conversation

@GokulPandi-M

@GokulPandi-M GokulPandi-M commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Motivation

Multi-sheet tscircuit designs export a KiCad root schematic that correctly names and references every child sheet, but the CLI writes only that root .kicad_sch file. The referenced child schematic files are missing from both the KiCad ZIP and the generated project directory.

KiCad therefore shows the expected sheet names in the hierarchy panel, while opening a child sheet produces a blank, unsaved page because its Sheetfile cannot be found. This makes an existing schematic look empty and prevents users from reviewing or editing the exported sheets.

Issue

image

Reproduction

The fixture declares power and control schematic sheets and assigns one component to each. The CLI integration tests cover both affected paths:

  • tsci export index.tsx -f kicad_zip
  • tsci build index.tsx --kicad-project

In both outputs, the root schematic references power.kicad_sch and control.kicad_sch, but neither child file is written. The converter already exposes the complete hierarchy through getOutputFiles(); the CLI paths currently use only getOutputString(), which returns the root file.

@GokulPandi-M GokulPandi-M changed the title repro: KiCad drops keepout exclusions and internally connected pad nets repro: KiCad exports omit hierarchical child schematic files Oct 8, 2026
@GokulPandi-M
GokulPandi-M marked this pull request as ready for review October 8, 2026 20:26

@imrishabh18 imrishabh18 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you recheck the deps version? Also the tscircuit.com export. Cause I have seen the hierarchical file being present in our export

@GokulPandi-M

Copy link
Copy Markdown
Contributor Author

Can you recheck the deps version? Also the tscircuit.com export. Cause I have seen the hierarchical file being present in our export

for sure i'll check again and let you know

@GokulPandi-M

Copy link
Copy Markdown
Contributor Author

Can you recheck the deps version? Also the tscircuit.com export. Cause I have seen the hierarchical file being present in our export

i have updated my board and dep to current version of tscircuit and i still have the issue @imrishabh18

image

@imrishabh18 imrishabh18 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Stack a PR with the fix, will approve both together and then merge

@GokulPandi-M

GokulPandi-M commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor Author

the fix pr #5236 i couldnt stack it , i dont access for that!! @imrishabh18

@github-actions

Copy link
Copy Markdown
Contributor

This PR has been automatically marked as stale because it has had no recent activity. It will be closed if no further activity occurs.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants