MixinNetwork / MixinNetwork/android-app
Key-value tables created in the database
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 503
- Forks
- 112
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 73
Description
Mixin database upgrade related data is stored in SharedPreferences and this data is not reliable. Key-value tables should be created in the database to store this data.
Contains the following data:
PREF_ATTACHMENT
PREF_ATTACHMENT_LAST
PREF_ATTACHMENT_OFFSET
PREF_FTS4_UPGRADE
PREF_SYNC_FTS4_OFFSET
PREF_BACKUP
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 referenced Constants.kt entries and trace where the listed SharedPreferences values are read and written. Replace their storage with database key-value tables while preserving the attachment, FTS4 upgrade, sync offset, and backup data; done means these values no longer depend on SharedPreferences.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- database, mobile
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100