-
Notifications
You must be signed in to change notification settings - Fork 49
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
Unexpected Behavior if State and Outcome have identical Names on branch "ros2-devel" #89
Comments
Effectively these outcomes are same as a state for connecting transitions. To avoid, follow a standard naming convention. We normally use PascalCase for state names, and snake_case for outcomes. |
Given this setup:
If you try to connect outcome
done
of StateA
to the outcomeA
of the behavior.The arrow automatically points to the State
A
itself, instead of the the outcomeA
of the behavior.If connected to the outcome
B
of the behavior, the arrow automatically points to the StateB
instead of the the outcomeB
of the behavior.The same inside a Concurrency Container: The Outputs can be connected.
The text was updated successfully, but these errors were encountered: