refactor(geometry): fold round-window deseam into extend_opening_mesh_through_host#1336
Conversation
…_through_host Follow-up to #1330. remove_internal_membrane was called explicitly before each of the 3 extend_opening_mesh_through_host call sites; a future void path (or the dead voids_2d fast path, if revived) could route an opening cutter through extend without deseaming and silently regress the two-extrusion round-window cut. Move the deseam to the top of extend_opening_mesh_through_host, the single helper every void subtract funnels through, so it can't be forgotten. Pure refactor: the 3 call sites now pass the raw opening_mesh, behaviour is identical (the helper already received the same depth_dir the explicit deseam used). Verified: round window still cuts clean (120 interior hole cells, unchanged); issue_635 11/11 + wall_opening_cut_regression + voids_production/submesh + issue_964/1167/1007/960 + door_window_calibration + engulfing_solid_void all green.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
ChangesDeseaming Centralization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Follow-up to #1330.
Why
remove_internal_membrane(the two-extrusion round-window deseam) was called explicitly before each of the 3extend_opening_mesh_through_hostcall sites. A future void path, or the currently-deadvoids_2dfast path if it were revived, could route an opening cutter throughextendwithout deseaming and silently regress the round-window cut. The fix relied on reviewer vigilance at every call site.What
Move the deseam to the top of
extend_opening_mesh_through_host, the single helper every void subtract funnels through, so no call site can forget it. The 3 call sites now pass the rawopening_mesh.Pure refactor, behaviour identical:
extendalready received the samedepth_dirthe explicit deseam used, and it stays a no-op for ordinary single-solid openings.remove_internal_membraneis now called from exactly one place;extend_opening_mesh_through_hoststill has exactly its 3 callers.Verification
issue_63511/11, pluswall_opening_cut_regression,voids_production/voids_submesh,issue_964/issue_1167/issue_1007/issue_960,door_window_calibration,engulfing_solid_void,opening_void_cut_local_frameall green.Summary by CodeRabbit