Skip to content

NoDL -> rclcpp code generation. Most minimal first workflow #52

@emersonknapp

Description

@emersonknapp

Description

Implement an end-to-end workflow illustrating how a user would take a NoDL input and actually create their node with it.

Open questions:

  • Is a superclass generated that the implementer inherits from?
  • How are callbacks for subscriptions/service servers/action servers registered?
  • How are parameter values received and updated?
  • What is the CMake-side usage?

Requirement: make the generator easily swappable so that we can provide several (for different client libraries, or for trying out new generation patterns)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    Ready

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions