simple-store
simple-store copied to clipboard
uber
Simple yet performant asynchronous file storage for Android
**Describe the bug** putString when wrapped with Completable.fromFuture() seems to run immediately. Verified via debugger. Maybe be specific to the instance when checking for said key before writing to SimpleStore...
When migrating to SS, you often have a step where writes go to both SS and the legacy storage. In this state, the SS is rarely used for performant read...
Currently simple-store provides no checking on the naming of it's keys. Instead, when sth. like `./` is used as a key, the store does unexpected things (moving wrong files etc.)....
We should separate the logic that uses an Android context for the folder location into a separate artifact, this will allow pure java modules to consume simple-store. (And might help...
The sample app has a kotlin activity consuming the library, document why this library is not in kotlin.
Might be worthwhile explaining or pointing to an explanation of why not use SharedPrefs _Originally posted by @jbarr21 in https://github.com/uber/simple-store/pull/25#issuecomment-494649681_
- [x] Add proto artifact to readme - [ ] Provide basic example - [ ] Document why proto is good for storage
Document why namespaces exist and what they are good for.