Closed twelho closed 3 years ago
We might even want to merge the kicad5-escape-fix
branch first and default to using the main branch of our fork as the dependency.
We might even want to merge the
kicad5-escape-fix
branch first and default to using the main branch of our fork as the dependency.
Yep that might be a good idea, I've now merged kicad5-escape-fix
to master
in our fork and updated this PR accordingly. Will merge now.
PR against upstream: https://github.com/productize/kicad-parse-gen/pull/9. The last commit to upstream was in 2019, so the project seems to be a bit dormant right now. Thus, I propose switching over to our own fork where I've fixed the escaping (in kicad5-escape-fix) for now. This eliminates the need for the
escape
andunescape
workarounds, as escaped characters are now correctly handled in the function responsible for input parsing in the library.cc @luxas @chiplet