Goal
After the shared SCAD convention adopts semantic domain-object names ending in _obj, review the reusable SCAD libraries and align their public/private APIs where appropriate.
Target repositories
At minimum review:
brainboxemb/lib.scad.hub75;
brainboxemb/lib.scad.clamps;
brainboxemb/lib.scad.mechint;
brainboxemb/lib.scad.forge and lib.scad.util only where code is domain-specific enough that a semantic object name is clearer than generic obj.
Rule
- domain objects:
panel_obj, clamp_obj, dovetail_obj, etc.;
- role-qualified objects:
source_*_obj, target_*_obj, etc.;
- bare
obj only for genuinely generic infrastructure.
Important
Do not mechanically rename released public API parameters without considering OpenSCAD named-argument compatibility and release/migration impact.
Track each library change with its own repository issue/PR and release evidence as needed.
Depends on the shared convention update tracked in #121.
Goal
After the shared SCAD convention adopts semantic domain-object names ending in
_obj, review the reusable SCAD libraries and align their public/private APIs where appropriate.Target repositories
At minimum review:
brainboxemb/lib.scad.hub75;brainboxemb/lib.scad.clamps;brainboxemb/lib.scad.mechint;brainboxemb/lib.scad.forgeandlib.scad.utilonly where code is domain-specific enough that a semantic object name is clearer than genericobj.Rule
panel_obj,clamp_obj,dovetail_obj, etc.;source_*_obj,target_*_obj, etc.;objonly for genuinely generic infrastructure.Important
Do not mechanically rename released public API parameters without considering OpenSCAD named-argument compatibility and release/migration impact.
Track each library change with its own repository issue/PR and release evidence as needed.
Depends on the shared convention update tracked in #121.