Skip to content

Clarify all-or-nothing CommandBuffer removal - #480

Open
voidsipp wants to merge 1 commit into
Ralith:masterfrom
voidsipp:fix/355-command-buffer-remove-docs
Open

voidsipp wants to merge 1 commit into
Ralith:masterfrom
voidsipp:fix/355-command-buffer-remove-docs

Conversation

@voidsipp

@voidsipp voidsipp commented Nov 3, 2026

Copy link
Copy Markdown

CommandBuffer::remove leaves every component untouched when the entity is missing any component in the requested bundle. The current docs make it sound like it removes whichever components are present.

This clarifies that behavior and adds a runnable example covering both a complete bundle and a missing component. No runtime behavior changes.

Tested with and without default features, including the new doctest. Formatting, documentation with warnings denied, and Clippy with warnings denied also pass.

Fixes #355.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document CommandBuffer.remove() will not remove any if it does not match all components

1 participant