Skip to content
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

Refactor ROS 2 node as a component #63

Merged
merged 1 commit into from
Nov 22, 2022
Merged

Refactor ROS 2 node as a component #63

merged 1 commit into from
Nov 22, 2022

Conversation

achim-k
Copy link
Collaborator

@achim-k achim-k commented Nov 21, 2022

Public-Facing Changes
Refactor ROS 2 node as a component

Description
Allows to run the ROS2 version both as standalone node or as a component.

For the standalone version we simply create a ComponentManager and load the foxglove bridge component. I'm not sure if this is best practice, but it has the advantage that it does not additional header files to be included which would require an additional refactoring.

Fixes #28

@achim-k achim-k enabled auto-merge (squash) November 21, 2022 23:36
@jhurliman jhurliman merged commit 6b2570d into main Nov 22, 2022
@jhurliman jhurliman deleted the achim/ros2_component branch November 22, 2022 00:18
achim-k added a commit that referenced this pull request Nov 25, 2022
**Public-Facing Changes**
Fix ros2 node not receiving any ros messages


**Description**
Fixes a regression introduced in #63. The created node was not added to
the executor and hence no ROS callbacks were executed.

We would have caught this regression with a proper smoke test in place
(#20)


<!-- link relevant GitHub issues -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Refactor ROS 2 node as a Component
2 participants