-
Notifications
You must be signed in to change notification settings - Fork 0
vNext Requests
Damian edited this page Jan 5, 2026
·
2 revisions
To continue the evolution of the system, the following feature requests have been made.
| Title | Description |
|---|---|
| Date | YYYY-MM-DD |
| Status | Considering / Explore / Nice-to-Have |
| Request | |
| Why? | Why is it important? |
| Risks |
| Title | Description |
|---|---|
| Date | 2025-12-25 |
| Status | Considering (v3.0?) |
| Request | After completing all substates, the parent state (Composite) should first go to OnState to perform any post-substate actions, and set the context.NextState(Result);, followed by the OnExit. Composite state would inherit from IComposite<TStateId> for transparency |
| Why? | Today, the parent state goes to OnExit which (1) isn't very clear that the user NEEDS to set the context.NextState(Result);. And, (2) this gives clarity to post-substate evaluations. |
| Risks | Breaking change for all composite states |