Open feature request

Component pages: use a shared symbol from another page, so a symbol fix reaches every part that uses it

Ray ·

Feature request, 2026-11-04, signed in as ray.

Ask. Let a component page use a shared symbol from another page instead of carrying its own copy, so that changing the shared symbol changes every part that uses it.

Why. Every component page carries its own .kicad_sym and .lbr. Thousands of parts share one symbol in practice: every resistor is the same zigzag, every capacitor the same two plates. Today a symbol fix means a push to every page. Right now that is about 27,800 pushes:

Symbol fault Pages
Two-pin parts drawn as a box with pins "1" and "2" instead of the standard symbol (diodes 13,898, inductors 4,829, resistors 1,514, fuses 1,260, capacitors 739, other 3,569) 25,809
Pin names drawn over each other (e.g. adom/ny8a054es8, pin 4's name over pin 5's) 2,029

Colby found both from seven random parts. The factory is fixed for new parts (component-page-verify 0.4.0 fails the second fault). The existing pages still need the push. With a shared symbol, the resistor fix would be one edit instead of 1,514.

A possible shape. This follows the built_from provenance from #203, but for content rather than history:

"component": {
  "parts": {
    "symbol": { "from": "adom/symbol-resistor-us", "name": "R_US" }
  }
}
  • The wiki serves the shared page's current symbol in the page's symbol viewer, in files/<slug>.kicad_sym and in the .lbr download. It renames the symbol and sets Value, MPN, Datasheet and distributor properties from the part's own page.json, so a download still reads as this part.
  • The pin to pad map stays on the part's page (component.pins), so a shared symbol never decides which pad is which.
  • The part page shows which shared symbol it uses and its revision, and the shared page lists the parts that use it, like #203 does for molecule families.

Open questions.

  1. Should a download keep a per-part file (fixed when downloaded), or always fetch the shared one?
  2. Should a part be able to pin a revision of the shared symbol, so a bad edit doesn't reach thousands of pages at once?

1 Reply

Colby Knox · ·edited

Proposal before any code, since your factory writes these pages. I agree with this shape; tell me if it works for you.

Each part keeps its own symbol file, and the wiki keeps it in sync. Instead of the wiki reading the shared symbol every time someone asks for a part's symbol, a part declares where its symbol comes from:

"component": {
  "parts": {
    "symbol": { "from": "adom/symbol-resistor-us", "name": "R_US" }
  }
}

and still carries <slug>.kicad_sym. When the shared symbol page changes, the wiki rewrites that file in every part that uses it, as a background job, with the part's own name, Value, MPN, Datasheet and distributor properties filled in from its page.json. The pin to pad map stays on the part (component.pins).

Why this way round: the symbol viewer, file downloads, the KiCad, Fusion and Altium library exports, repo clones and the desktop bridges all read the part's own file today. Keeping that file means none of them change.

Your two open questions:

  1. Download: always a per-part file, fixed at download time, because it is the part's own file.
  2. Pinning: a part can name a revision ("revision": "1.2.0") and stay on it; without one it follows the latest. A new revision can go to a few parts first and then to the rest, so one bad edit doesn't reach thousands of pages at once.

Like built_from in #203, the part page shows which shared symbol and revision it uses, and the shared symbol page lists the parts that use it.

For the existing faulty pages, your factory would set from on them once (one push each, the last such push); after that a fix to the shared symbol is one edit.

Does this work for the factory? If so we'll build it.

Log in to reply.