feat: eliminate need to pass context to states #26
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.
IContext
object. Instead, the context is provided when a state is attached to a logic block as the logic block's active state. Eliminating contexts in state constructors simplifies serialization and reduces typing.OnAttach
andOnDetach
, which can and should be used for setting up a state instance. These differ fromOnEnter
andOnExit
, respectively, as all callbacks registered viaOnAttach
andOnDetach
will be called on the state instance whenever the state changes, whereasOnEnter
andOnExit
are only invoked when entering and exiting relevant states with respect to the type hierarchy.OnAttach
andOnDetach
are great for subscribing to events or other long-running operations that need to be cleaned up on a per-instance basis. Before, previous state instances would be implicitly retained in memory if relevant to the active state's type hierarchy. Now, LogicBlocks is more theoretically sound as only one state is active and retained at any given time.context
parameter inGetInitialState
.Get<TDataType>()
method available to states.