You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: Aggregate state changes caused by service/entity operations.
While write [S1-> S2x S3] and write [S2,S3-> S4] work I cannot model something like:
write [S1->S2, S1->S3, S2->S4, S3->S4]
My workaround is to model one operation per state transition, but the system that I model has a single updateStatus() interface that can cause arbitrary transitions.
The text was updated successfully, but these errors were encountered:
socadk
changed the title
More flexibility for modeling State transitions: m
More flexibility for modeling state transitions
Jul 8, 2021
Context: Aggregate state changes caused by service/entity operations.
While
write [S1-> S2x S3]
andwrite [S2,S3-> S4]
work I cannot model something like:My workaround is to model one operation per state transition, but the system that I model has a single updateStatus() interface that can cause arbitrary transitions.
The text was updated successfully, but these errors were encountered: