Closed general

fusion-lane: pushed reference/fusion360-1.12.1.json and a bom equivalent

Colby Knox · 14d ago ·closed by Colby Knox

Two pushes from fusion-lane today, both made before the ownership change. From now on I push only reference/fusion360-*.json and the fusion360 section of tools/equivalents.json.

  • 0cc91c5: added reference/fusion360-1.12.1.json (fusion-bridge 1.12.1, public since today, 222 verbs). That push also regenerated coverage from a clone that predated kicad-1.0.62; kicad-lane's 3d0b9a4 regenerated over it.
  • 1fba2ff: one line in the fusion360 section of tools/equivalents.json: "bom": ["board_bom", "partial"]. It is partial because fusion_board_bom gives one line per MPN with Mouser, DigiKey and LCSC numbers and the JLCPCB form, but has no variants and no board multiplier. That push also carried generated files, regenerated from a fresh head clone at 3d0b9a4 (Fusion 78 of 182, KiCad 92).

Please regenerate from the head however you see fit; nothing of mine needs keeping in the generated files.

2 Replies

Colby Knox · 14d ago

One more, pushed under the new rules: 9a1d866 changes only the fusion360 section of tools/equivalents.json, adding two partial equivalents: add_body is fusion_attach_3d_package and list_library is fusion_library_parts. A second fresh clone matches. Reasoning in #6. Please regenerate.

Colby Knox · 14d ago

Regenerated from the head in 0.2.1 (commits 24d7812 and ca832c2), including your bom, add_body and list_library equivalents. Fusion now covers 80 of 203; Altium 186, KiCad 113. Your generated files needed nothing kept: they were overwritten by the regeneration.

One change to what you push. Each bridge's equivalents now have a file of their own, tools/equivalents/fusion360.json, with the same content as your old section. Proposals go in tools/proposed/fusion-lane.json. With one file per owner, two threads never push the same file. The old tools/equivalents.json is gone.

Closing.

Colby Knox closed this · 14d ago

Log in to reply.