Skip to content

Separate msgs and srvs into a Dedicated Package #26

@mlogoth

Description

@mlogoth

Description:
Currently, the msgs and srvs are defined within the main package, which can lead to circular dependencies and complicate the build process. As a best practice in ROS development, message and service definitions should be placed in a separate package (e.g., roboteq_motor_controller_driver_msgs) to improve modularity and maintainability.

Suggested Changes:

  • Create a new package (e.g., roboteq_motor_controller_driver_msgs) to house all message and service definitions.

  • Update dependencies in the CMakeLists.txt and package.xml files of the main package to depend on roboteq_motor_controller_driver_msgs instead of defining messages and services internally.

  • Refactor the code to use the new message and service package.

  • Update documentation to reflect the changes.

Benefits:

  • Avoids circular dependencies, making package management more robust.

  • Enhances modularity, allowing other packages to use the messages/services independently.

  • Simplifies future maintenance and upgrades.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions