[Feature request]: Add a map name field to the MapRegionUpdate message
Maintainers usually reply within 15 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
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.
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
- Dominant language
- Python
- Stars
- 10
- Forks
- 9
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from open-rmf/next_gen_prototype
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 8/100
open-rmf/next_gen_prototype#81 ·
Maintainers usually reply within 15 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
open-rmf/next_gen_prototype#80 ·
Maintainers usually reply within 15 days
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
open-rmf/next_gen_prototype#66 ·
Maintainers usually reply within 15 days
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
open-rmf/next_gen_prototype#65 · 2 comments ·
Maintainers usually reply within 15 days
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 42/100
open-rmf/next_gen_prototype#57 ·
Maintainers usually reply within 15 days
All issues in open-rmf/next_gen_prototype
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
deepchem/deepchem#5289 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
UKGovernmentBEIS/inspect_evals#2892 · 1 comment ·
Maintainers usually reply within 1 day
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affectedPossibly taken @grelinfo claimed this today. Opendocumentation priority:low size:S
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
alphacrack/readme2demo#293 ·