Direct users to commands.set_state instead of NextState #15127
Open
Description
Second thoughts, I'd like this to be the standard way of updating states.
Using commands:
- implies the deferred nature of this operation
- reduces clutter associated with
NextState, especially when many are used - does not make problems with system ambiguities worse
- allows for falliable operations with a warning, which we will need when the traits get unified and not everything will use
NextState - with a different command you can force the transition to happen immediately without writing an exclusive system
I don't think this change has to happen now, but it looks like a better API overall to me
Originally posted by @MiniaczQ in #15083 (comment)
Metadata
Assignees
Labels
App-level states machinesA section of code that is hard to understand or changeQuite challenging from either a design or technical perspective. Ask for help!This issue requires design work to think about how it would best be accomplishedThere are nontrivial implications that should be thought through