open-rmf / open-rmf/next_gen_prototype
[Feature request]: Add a map name field to the MapRegionUpdate message
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 10
- Forks
- 9
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 2
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
Description
It is not uncommon for us to deal with multiple maps (for instance, in a multi-level deployment). Currently the MapRegionUpdate message does not define a map_name. Note that if we resolve #5, we resolve this ticket.
Implementation Considerations
No response
Alternatives
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the schema or message definition for MapRegionUpdate and check how related message changes are tested. Confirm whether issue #5 already covers this request; done means the message exposes a map_name field, unless that issue supersedes this work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100