Fail to load sheets in subdirectory

[Vincent-Dalstra]

This happens with the standalone app, both for github links and dropping files.

The problem occurs when there are hierarchical sheets in subdirectories, rather than all in the root directory.

(Fails) https://github.com/Vincent-Dalstra/ESP_bare_chip_test_board/tree/a5cf98b5a4ff008193808d2139580ce6fd54707c

==========

I've isolated the problem in a simpler project as well:

Single sheet, no subsheets
(Good) https://github.com/Vincent-Dalstra/ESP-flash/tree/06fc9d384f3aba9f03f10750e34abc952235a4b2

Added subsheet, stored in subsheet/usb.kicad_sch
(Fails) https://github.com/Vincent-Dalstra/ESP-flash/tree/479d80dde0840f8e16035f79bf4be6d6ebb9c71d

Moved the subsheet into the root folder , usb.kicad_sch
(Good) https://github.com/Vincent-Dalstra/ESP-flash/tree/af3d36cd5e6d727cb4edfe8559778281b62d5704

[Vincent-Dalstra]

Going to take a crack at solving this myself. Filing an issue first as per contributing guidelines.

My workflow makes heavy use of subsheets, and it's nice to store them tidily in a subdirectory. It makes sense to try and fix the bug, if possible, rather than change what I'm doing. My language is C though, not typescript, so we'll see how it goes : )

[Vincent-Dalstra]

This was definitely not the best way to learn Typescript.

Current progress linked below. It only works for (some) URL's, and breaks existing tests, hence no pull-request. It's a start.

https://github.com/Vincent-Dalstra/ESP_bare_chip_test_board/tree/a5cf98b5a4ff008193808d2139580ce6fd54707c

P.S. If anyone has tips on how to build and run this locally, rather than using github-actions each time, that would make things considerably easier.

[theacodes]

Hey @Vincent-Dalstra, you should be able to develop locally by

• installing node
• running npm install to install the dependencies needed
• running npm run serve to run a local instance that automatically rebuilds when you make changes

Let me know if any of that doesn't work for some reason.

[Vincent-Dalstra]

Works like a charm.

Hah, looking at my bash history, I was so close: I figured out that npm run lint and npm run test did things (inferred from the github actions), but didn't find this one. I see now that there's a list in packages.json. npm run format is handy.

Thank you very much for the help.

[theacodes]

Glad I could help! Thank you for taking a look at fixing this issue. :)

…

On Thu, Jul 24, 2025, 10:57 AM Vincent-Dalstra ***@***.***> wrote: *Vincent-Dalstra* left a comment (theacodes/kicanvas#119) <#119 (comment)> Works like a charm. Hah, looking at my bash history, I was so close: I figured out that npm run lint and npm run test did things (inferred from the github actions), but didn't find this one. I see now that there's a list in packages.json. npm run format is handy. Thank you very much for the help. — Reply to this email directly, view it on GitHub <#119 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB5I4YLOFOS5SMHX6JNUQT3KDX5XAVCNFSM6AAAAACBSIWKY6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCMJTHAYDAMRUGA> . You are receiving this because you commented.Message ID: ***@***.***>

[XiangYyang]

It was fixed in #188