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.

Sign up for GitHub

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

Jump to bottom

[subscribers] force the user to provide a qos profile #102

Closed

stonier opened this issue Sep 17, 2019 · 0 comments · Fixed by #104

Labels

component:behaviours type:enhancement

Milestone

Member

stonier commented Sep 17, 2019

Given that it is so much more critical in ROS2 than ROS1, it is probably worth forcing the user to think about it.

stonier added type:enhancement component:behaviours labels

stonier added this to the 1.1 - Dashing milestone

stonier mentioned this issue

[subscribers] stricter arg handling #104

Merged

stonier closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment