dimensionalOS / dimensionalOS/dimos
Separate the tf system from the module base
Open
Nobody has claimed this yet.
core
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 808
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 233
Description
Every module currently gets self.tf machinery from the module base even though most modules never touch tf, and the lazy init on publish/get papers over that rather than fixing it. A class decorator to opt-in a class forself.tf would be ideal.
Synced from DIM-1464 by jeff
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 reading the module base and tracing where self.tf is initialized and used by publish/get. Identify how a class decorator could opt modules into the tf system, then verify that modules without the opt-in no longer receive the machinery while opted-in modules retain it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100