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

[Feature Request] Message class for other Motion types in behavior service #65

Open
ersaraujo opened this issue Oct 26, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@ersaraujo
Copy link
Member

Describe the feature request.

Mapper to other motion messages

Describe the scenario use case.

Use to make proto output message.

@ersaraujo ersaraujo added the enhancement New feature or request label Oct 26, 2024
@ersaraujo ersaraujo added this to the CBR-Release milestone Oct 26, 2024
ersaraujo added a commit that referenced this issue Oct 31, 2024
## Overview 👀

This PR add message mappers to behavior service and a generic use in
`behavior_processor`

- Add robotId message class
- Add Output and Behavior message class
- Add Motion (GoToPoint) message class

### Notes 🗒️ 
The following implementations are pending:
1. Other motion types messages
#65
2. Planning message #64
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant