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.
Prior to this change, Bevy
SubStates
do not work. Running the new example gives this panic:With my fix, the new example works:
I also added a test to prove it works.
The change seems sensible to me: We shouldn't look up the
State<S>
resource unless there is at least some next state, so it's just moved down. The reason this can't be at the top is that when you add a sub state in Bevy usingapp.add_sub_state::<S>()
, Bevy doesn't seem to initialise theState<S>
resource, not sure why.