-
Notifications
You must be signed in to change notification settings - Fork 17
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
Shape.workplane can now accept a cadquery.Plane object #84
Conversation
…n-energy/paramak into workplane_accepts_cq_plane
Codecov Report
@@ Coverage Diff @@
## develop #84 +/- ##
===========================================
- Coverage 98.17% 97.86% -0.31%
===========================================
Files 76 75 -1
Lines 4873 4875 +2
===========================================
- Hits 4784 4771 -13
- Misses 89 104 +15
Continue to review full report at Codecov.
|
It looks like jupyter cadquery is trying to jsonify a |
I've rebuilt the dockerimage that the tests run on and rerun the tests. Looks like this PR is now working. There must have been a problem with the dockerimage contents that appears to have been fixed now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is precisely what I was requesting; thanks @RemDelaporteMathurin !
Super, I guess we just need to change the docstring a bit and add a test if that is ok. I can do these if that helps |
Thanks for another nice feature @RemDelaporteMathurin |
Proposed changes
Linked to #81.
This PR allows user to define the workplane from a cadquery.Plane object, which is defined by an origin point and a normal vector.
This normal vector is then the extrusion vector.
Usage
Types of changes
What types of changes does your code introduce to the Paramak?
Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.