Additional doc aliases for WindingOrder in bevy_math
#13065
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add "Orientation" for `WindingOrder` itself - Add "AntiClockwise" for `CounterClockwise` variant - Add "Collinear" for `Invalid` variant Signed-off-by: Nullicorn <git@nullicorn.me>
|
Welcome, new contributor! Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨ |
matiqo15
added
C-Docs
alice-i-cecile
approved these changes
Apr 22, 2024
NthTensor
approved these changes
Apr 22, 2024
mockersf
approved these changes
Apr 22, 2024
mockersf
added
the
S-Ready-For-Final-Review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
Adds a few extra
#[doc(alias)]entries to thebevy_math::primitives::WindingOrderenum and its variants to improve searchability.Solution
WindingOrderitselfCounterClockwisevariantInvalidvariantThese alternate terms seem to be quite common, especially in the contexts of rendering and collision-detection.