Design Reconsideration for ros2doctor. #1091
Description
Description
For now, ros2doctor calls the corresponding APIs to construct the report details such as endpoints information like topics, services and actions.
But basically those are already implemented in each command line interface such as ros2 topic list, ros2 service list and ros2 action list. IMO this is redundant implementation and not cost effective for maintenance.
instead, something we can consider here is that, ros2doctor only issues the listed command line interfaces to construct the report. in this way, ros2doctor only relies on the command line interfaces without having the almost same redundant implementation.
Motivation
For cost effective maintenance.
In this design, we only need to manage the what CLIs are issued on ros2doctor, that is really easy to add and remove as well.
Design / Implementation Considerations
No response
Additional Information
No response