OADA automatic sync
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Some work still needs to be done to prevent infinite cycles between oada clouds syncing among themselves.
This could potentially be solved by adding an extension to oada that would store a change document (maybe a hash) that describes it's origin.
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 does not identify files, tests, or an entry point. Start by locating the server's automatic synchronization path and reviewing how changes are propagated between OADA clouds; done means preventing infinite sync cycles with a documented origin-tracking approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100