Skip to content

Conversation

@rmsthebest
Copy link
Contributor

Objective

Update the example to avoid teaching new people that the recommended way of updating a component is to re-insert it.

Solution

Instead of inserting the component every time we want to change it, update the value.

Testing

  • Did you test these changes? If so, how? Yes, ran the example
  • Are there any parts that need more testing? I don't think so?
  • How can other people (reviewers) test your changes? Is there anything specific they need to know? Run the example, press left and right mouse.
  • If relevant, what platforms did you test these changes on, and are there any important ones you can't test? (linux/wayland)

@alice-i-cecile alice-i-cecile added D-Trivial Nice and easy! A great choice to get started with Bevy C-Examples An addition or correction to our examples A-Windowing Platform-agnostic interface layer to run your app in S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it labels Nov 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Windowing Platform-agnostic interface layer to run your app in C-Examples An addition or correction to our examples D-Trivial Nice and easy! A great choice to get started with Bevy S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants