Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More flexibility for modeling state transitions #296

Open
socadk opened this issue Jul 8, 2021 · 0 comments
Open

More flexibility for modeling state transitions #296

socadk opened this issue Jul 8, 2021 · 0 comments

Comments

@socadk
Copy link
Contributor

socadk commented Jul 8, 2021

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.

@socadk socadk changed the title More flexibility for modeling State transitions: m More flexibility for modeling state transitions Jul 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant