-
Notifications
You must be signed in to change notification settings - Fork 6
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
Non-null state accepted as final state #1130
Projects
Comments
This raises the question what we do with sessions that don't end (e.g. a proxy)? |
I think we should implement #700 where we decided to remove the need for an explicit definition of a final state. |
I forgot about #700 - I agree. |
treiher
added a commit
that referenced
this issue
Sep 20, 2022
treiher
added a commit
that referenced
this issue
Sep 20, 2022
treiher
added a commit
that referenced
this issue
Sep 22, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following session specification must not be accepted, as the final state is not a null state. A final state is never executed, so it doesn't make sense to define actions or transitions for it.
The text was updated successfully, but these errors were encountered: