A Part holds exactly one solid (withdraw the multi-body Part); open solids are shown, not a Part by NiJingzhe · Pull Request #83 · PhySpace/SimpleCADAPI

part: a Part holds exactly one solid (the constructor refuses several; make_part_rpart and Part lose `bodies=`)

NiJingzhe

and

claude

committed

654a6d3

python glue + replay: follow the one-solid Part (pickle through Body, refuse a recorded multi-solid make_part_rpart)

NiJingzhe

and

claude

committed

2c99826

artifacts: a part definition holds one solid (drop BodyRef, `solid_cache.bodies` and profile 3)

NiJingzhe

and

claude

committed

9fb9401

design-docs: record the decision that a Part holds exactly one solid (and mark multi-solid-design.md superseded)

NiJingzhe

and

claude

committed

6c49c88

runtime + preview: several open solids are shown side by side, but are no longer a Part

NiJingzhe

and

claude

committed

90fe84a

scene + exporters: a Part is drawn, exported and measured from its one body (no per-body branches)

NiJingzhe

and

claude

committed

2029bee

api: remove the helpers that only existed for a Part of several bodies

NiJingzhe

and

claude

committed

84aab45

editor: several open solids have no product until the author picks one (use_as_product), and say so

NiJingzhe

and

claude

committed

d415647

editor-web: the "model shown" log says what the header says (open solids are not parts)

NiJingzhe

and

claude

committed

f016a14

AGENT.md: record how to rebuild the C++ module here, and why the obvious commands fail

NiJingzhe

and

claude

committed

910df75

tests: replace the multi-body Part tests by tests of the one-solid rule (and of what the audit found broken)

NiJingzhe

and

claude

committed

0307aaa

cpp: comments no longer describe multi-body Parts

NiJingzhe

and

claude

committed

7e2e996

cleanup: remove the package's per-body blob path check, and comments that still said "multi-body part"

NiJingzhe

and

claude

committed

ba19f43

docs/api: the API pages say a Part holds exactly one solid (drop `bodies=`, multi-body wording and inspect_body_overlaps_rlist)

NiJingzhe

and

claude

committed

6441107

docs/skill: domain, discipline, workflow and guide pages follow the one-solid Part (and the open-solids rule)

NiJingzhe

and

claude

committed

fb50a97

docs/skill: scadpkg-format says a part definition holds one solid (no solid_cache.bodies, no profile 3)

NiJingzhe

and

claude

committed

01852ed

changelog + SDK_DEFECTS: record that a Part holds one solid again (and what the multi-body notes now mean)

NiJingzhe

and

claude

committed

d0040a7

docstrings: the source of the API pages say a Part holds one solid (and the pages are regenerated from them)

NiJingzhe

and

claude

committed

a0923a6

tests: the cell-cache test of restored Pieces makes its Part from one piece

NiJingzhe

and

claude

committed

b56634e

tests: the editor's API index test expects Part to take `body` and no `bodies`

NiJingzhe

and

claude

committed

f60f698

AGENT.md: write down how commits are organised (one decision per commit, with the reasons from the discussion)

NiJingzhe

and

claude

committed

0a961d1

cpp: format part.hpp and bind_product_values.cpp with clang-format 18.1.8 (CI's clang-format job failed on them)

NiJingzhe

and

claude

committed

695a03a

tests: do not depend on the order of the names a single cell defines (Python 3.12 CI failed on it)

NiJingzhe

and

claude

committed

5efd5bb

Navigation Menu

Repository navigation

A Part holds exactly one solid (withdraw the multi-body Part); open solids are shown, not a Part - #83

A Part holds exactly one solid (withdraw the multi-body Part); open solids are shown, not a Part#83
NiJingzhe merged 23 commits into
devfrom
fix/part-holds-one-solid

Commits on Nov 9, 2026

part: a Part holds exactly one solid (the constructor refuses several; make_part_rpart and Part lose `bodies=`)

python glue + replay: follow the one-solid Part (pickle through Body, refuse a recorded multi-solid make_part_rpart)

artifacts: a part definition holds one solid (drop BodyRef, `solid_cache.bodies` and profile 3)

design-docs: record the decision that a Part holds exactly one solid (and mark multi-solid-design.md superseded)

runtime + preview: several open solids are shown side by side, but are no longer a Part

scene + exporters: a Part is drawn, exported and measured from its one body (no per-body branches)

api: remove the helpers that only existed for a Part of several bodies

editor: several open solids have no product until the author picks one (use_as_product), and say so

editor-web: the "model shown" log says what the header says (open solids are not parts)

AGENT.md: record how to rebuild the C++ module here, and why the obvious commands fail

tests: replace the multi-body Part tests by tests of the one-solid rule (and of what the audit found broken)

cpp: comments no longer describe multi-body Parts

cleanup: remove the package's per-body blob path check, and comments that still said "multi-body part"

docs/api: the API pages say a Part holds exactly one solid (drop `bodies=`, multi-body wording and inspect_body_overlaps_rlist)

docs/skill: domain, discipline, workflow and guide pages follow the one-solid Part (and the open-solids rule)

docs/skill: scadpkg-format says a part definition holds one solid (no solid_cache.bodies, no profile 3)

changelog + SDK_DEFECTS: record that a Part holds one solid again (and what the multi-body notes now mean)

docstrings: the source of the API pages say a Part holds one solid (and the pages are regenerated from them)

tests: the cell-cache test of restored Pieces makes its Part from one piece

tests: the editor's API index test expects Part to take `body` and no `bodies`

AGENT.md: write down how commits are organised (one decision per commit, with the reasons from the discussion)

cpp: format part.hpp and bind_product_values.cpp with clang-format 18.1.8 (CI's clang-format job failed on them)

tests: do not depend on the order of the names a single cell defines (Python 3.12 CI failed on it)