-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Cannot add behaviors to parent composite states #5522
Comments
@sidharthv96 I would like to try working on this issue if support is desired, but first I want to understand if it makes sense to have a new shape or modify the current cluster shape to support multiple descriptions.
I noticed that there is this specific shape for the state with description, could we possibly reuse some of the code from there?
|
Help is always welcome 😇 State diagram is currently undergoing major rework on the rendering part, by @knsv and @ashishjain0512. So it might be a good idea to wait till that's done, or check with them if their refactoring will interfere with the work you're planning. |
Ohh thanks! I'll take a look and understand, but I believe it's also better to wait :) |
@igorwessel @knsv @ashishjain0512 I think I have a good workaround for this issue here: #5966 Hopefully it is an easy layout fix. |
Description
You can add a UML-style behavior ("trigger [guard] / action()") to state nodes in diagrams, but you cannot add a behavior to a parent node.
Steps to reproduce
See description
Screenshots
Code Sample
No response
Setup
Suggested Solutions
No response
Additional Context
Proposed documentation about adding behaviors to state machines: #5512
The text was updated successfully, but these errors were encountered: