digidem / digidem/comapeo-cloud-app
security(vault): migrate structured local data to encrypted repositories
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 29
Description
Status: spec-in-progress\nParent tracker: #278\nDependencies: #238 and #301.\n\nSpec shell. Owns migration of structured territorial/application records from the legacy plaintext Dexie schema into the canonical encrypted-record repository, replacement of direct plaintext Dexie access, opaque remote identity/dedup semantics, and sensitive persisted selection cleanup. No binary cache migration or lock UI in this child.
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
Start with the parent tracker #278 and dependencies #238 and #301, then trace the legacy plaintext Dexie schema and canonical encrypted-record repository. Done means structured territorial and application records use the encrypted repository, direct plaintext Dexie access is replaced, remote identity and deduplication remain opaque, and sensitive persisted selections are cleaned up; binary cache migration and lock UI are out of scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- database, mobile, security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100