-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
velocityXYZ
names are violating conventions
#459
Comments
additionally, seeing how common this mistake is, we should add this as an example in the conventions. |
Re-posting what I said on discord:
Additionally, this would contradict the Coordinates convention, which goes so far as to specify "velocityX, not xVelocity"
When this was brought up on discord it seemed like there was a distinct lack of agreement that the current "velocityX" order is less natural. There was also disagreement on the current "velocityX" being less natural in #458 where, to my knowledge, this discussion started. Start of discussion. |
I agree with @supersaiyansubtlety that
|
The issue is actually about |
I'm not sure I support this change anymore, but if anyone has another argument for it I'd love to hear it. otherwise, I'm closing the issue. |
as discussed in this pr and on discord,
velocityXYZ
reads much less naturally thanxyzVelocity
, which means thatvelocityXYZ
names are in violation of the conventions, specifically this section of "general":The text was updated successfully, but these errors were encountered: