Hard-code group values for ROS2?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20
- Forks
- 24
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 17
Description
Bloom apparently hard-codes the values for which message generators they use. We extract them from the group dependencies.
However, group deps are completely ignored by bloom so maybe we shoudl do the same.
Contributor guide
No contributing guide indexed for this repository
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
The issue names Bloom, group dependencies, and message generators but no files or tests. Start by tracing where vinca extracts group dependencies and selects message generators, then compare that behavior with Bloom's handling. Done requires a decided policy for hard-coding or deriving the group values and corresponding test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100