We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From thread #426 (comment)
Similarly, toArray has a quirk where it suggests a QuaternionTuple return type which isn't always the case.
Just filing an issue for this so I can follow the CONTRIBUTING branch naming guidelines.
I'll submit a PR to align the fromArray and toArray types for Quaternion with how it's written for Vector3.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
From thread #426 (comment)
Similarly, toArray has a quirk where it suggests a QuaternionTuple return type which isn't always the case.
Just filing an issue for this so I can follow the CONTRIBUTING branch naming guidelines.
I'll submit a PR to align the fromArray and toArray types for Quaternion with how it's written for Vector3.
The text was updated successfully, but these errors were encountered: