-
Notifications
You must be signed in to change notification settings - Fork 418
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
Expose get_node_names API from node. #508
Conversation
Signed-off-by: Sriram Raghunathan <rsriram7@visteon.com>
Signed-off-by: Sriram Raghunathan <rsriram7@visteon.com>
Code change looks good to me. Though this raises the question of how we want users to access the node_graph API in the future as just forwarding all these functions on the node interface doesn't seem ideal, ticketed at #509 |
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.
lgtm
CI (build up to |
CI looks ok and change is approved, merging. Thanks for the PR @sriramster ! |
Oops, I failed to click merge (edit: now it's merged) |
* Enable incremental parameter yaml file parsing. Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com> * Parse CLI parameter files and overrides in rcl. Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com> * Address peer review comments. Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
* Document QoS Policy overrides Signed-off-by: Anas Abou Allaban <aabouallaban@pm.me>
Exposing get_node_names API from node interfaces rather than node_graph ones.