[BUGFIX] Allow Scoped Modules to be active while targeting a nested substate #6490
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.
Vocabulary
PlayStatewhen using the chart editor.These are your vocabulary words for today's PR, thank you for re-experiencing the horrors of Language Arts class.
Description
Unfortunately, the
ModuleHandlercallEventmethod only checks if the current state or substate on that state is active. This means that any nested substate won't activate scoped modules.This PR makes sure this behavior doesn't happen by doing a recursive search through every substate, and checking if the substate is the state specified for the scoped module.