-
Notifications
You must be signed in to change notification settings - Fork 2k
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
fixed problem with type conversions in Line3D #4080
base: main
Are you sure you want to change the base?
fixed problem with type conversions in Line3D #4080
Conversation
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
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.
Thanks!
test.py
Outdated
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.
Did you mean to commit this?
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.
No. Should I?
Co-authored-by: Aarush Deshpande <[email protected]>
Co-authored-by: Aarush Deshpande <[email protected]>
Overview: What does this pull request change?
It prevent for passing wrong type of data in Line3D and Arrow3D.
Motivation and Explanation: Why and how do your changes improve the library?
It is inspired by this discord post, where point into Arrow3D has been passed as list of integers instead of floats, which broke subtraction during the Rotation. Right now, data will be automatically converted into the float64 format.
Links to added or changed documentation pages
Further Information and Comments
Reviewer Checklist