dimensionalOS / dimensionalOS/dimos
Enforce Rust topic message types match what is expected on that port
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
There's no guarantee that the topics passed to Rust ports match the expected type. We are just trusting that it is done correctly on the Python side, but we should probably check specifically.
This would also let us reduce a bit of the boiler plate specifying encode/decode functions which in general are just the default functions for the message type.
Synced from DIM-1622 by andrew
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
Start by locating the Rust port definitions and the Python-side topic and message wiring mentioned in the issue. Trace how expected message types and encode/decode functions are currently specified; done means mismatched topic types are rejected and redundant default encoder/decoder boilerplate can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100