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

Make ros_type_name and gz_type_name optional in ros_gz_bridge #493

Open
azeey opened this issue Feb 5, 2024 · 0 comments
Open

Make ros_type_name and gz_type_name optional in ros_gz_bridge #493

azeey opened this issue Feb 5, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@azeey
Copy link
Contributor

azeey commented Feb 5, 2024

Desired behavior

Since the ROS and Gazebo topic names are provided to ros_gz_bridge, it seems possible to determine the topic type names automatically. If there is a one-to-many or many-to-many mapping, we can either bail or provide sane defaults.

Alternatives considered

n/a

Implementation suggestion

n/a

Additional context

n/a

@azeey azeey added the enhancement New feature or request label Feb 5, 2024
@azeey azeey moved this from Inbox to To do in Core development Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: To do
Development

No branches or pull requests

1 participant