-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Second-Body Extrude Selection #5456
base: main
Are you sure you want to change the base?
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5456 +/- ##
=======================================
Coverage 86.02% 86.02%
=======================================
Files 95 95
Lines 35754 35754
=======================================
Hits 30757 30757
Misses 4997 4997
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
…ittyCAD/modeling-app into max-fillet-pipes-to-wrong-body
…ittyCAD/modeling-app into max-fillet-pipes-to-wrong-body
Refactors
getPathToExtrudeForSegmentSelection
to derive the extrude from thesegment
orsweepEdge
artifact
rather than scanning bypath ID
. Thanks @Irev-Dev for help !This ensures the correct body is always selected when adding fillets/chamfers (previously, the second extrude could mistakenly point to the first). (in piped cases)
Introduces
getSweepArtifactFromSelection
to retrieve the parent sweep from either a segment or a sweepEdge.Adds two new test cases verifying that a second extrude referencing the first extrude’s face is correctly identified (both piped and standalone).
We now reliably link selections (segments/edges) to the right extrude, eliminating the “fillet on the wrong body” bug.
Closes: #5358