-
Notifications
You must be signed in to change notification settings - Fork 69
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
Make name and namespace mandatory in ComposableNodeContainer, remove deprecated alternatives #189
Conversation
…deprecated alternatives Signed-off-by: Ivan Santiago Paunovic <ivanpauno@ekumenlabs.com>
This partially addresses #123. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not uber convinced we should be making name and namespace mandatory anywhere BUT we control this container executable so I guess it's fine.
LGTM pending green CI !
One other thing to note; if we go forward with this, please add a note to https://index.ros.org/doc/ros2/Releases/Release-Galactic-Geochelone/ , since this is a change in behavior. |
In Foxy, it was already mandatory both the name and the namespace. See eloquent code. |
If anything, we should add a patch to Foxy to produce a better error message from the ComposableNodeContainer |
See #191 |
Based on discussion in #185, the name and namespace are mandatory.
I think that the intention was to check that, but it was overlooked when adding support for the deprecated name of the argument.
This delete the deprecated name (they were deprecated before Foxy release), and now it's checked.