forgecad-component-model

Multi-part CAD coordinate bugs are fixed by enforcing origin-only part geometry and using connector-based face-to-face composition. This standardizes how parts are positioned, eliminating manual translate hacks and inconsistent assembly-space offsets.

The best way to structure ForgeCAD components is making each part a pure function that returns shape, connectors, and metadata. The parent assembly then composes parts using addPart and connect couplings with zero coordinate math.

Assemblies break from brittle structural coordinate math and sibling imports. Enforcing strict prop-down and metadata-up data flow isolates parts, ensuring computed values travel upward as metadata without direct sibling dependencies.

You validate TypeScript component architecture by using verify.* methods instead of console logging. This enforces the ForgeCAD component model and confirms that parts meet correctly via connector interfaces without structural offsets.

You should not use translate hacks to position parts. The ForgeCAD component model requires origin-only part geometry and defines face-to-face connector interfaces so parts meet correctly without manual coordinate manipulation.

Yes, refactoring multi-part projects requires each part to return a shape, connectors, and metadata object. The assembly then composes these parts using addPart and connect couplings, enforcing strict prop-down and metadata-up data flow.