Docs: Specify that Relationships may only be one-to-many or one-to-one#23934
Merged
alice-i-cecile merged 1 commit intobevyengine:mainfrom Apr 22, 2026
Merged
Conversation
Specify that relationships may only be one-to-many at most
kfc35
added
C-Docs
kfc35
added
S-Needs-Review
alice-i-cecile
approved these changes
Apr 22, 2026
alice-i-cecile
added
S-Ready-For-Final-Review
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This may be deduced by observing that the
Relationshipcomponent only stores one entity ID, but in my opinion, to become aware of such a fundamental limitation, one should not need to look at the implementation and do some deducing.Tested by running
cargo doc --no-depsfrom the root of the repository and opening the relevant webpage.