Key/value preferences persisted in the offline database, plus the storage report.
Narrower than the other sub-modules on purpose: it exposes no init() and no _db, because
its three members are all a consumer needs. getStorageStats sits here rather than in a
store of its own since it reports on the whole database — quota, usage, and the row counts
that make a « why is it full » answer possible.
Values are unknown on both ends: preferences are integrator-defined, so the core stores
them without asserting a shape it does not own.
Key/value preferences persisted in the offline database, plus the storage report.
Narrower than the other sub-modules on purpose: it exposes no
init()and no_db, because its three members are all a consumer needs.getStorageStatssits here rather than in a store of its own since it reports on the whole database — quota, usage, and the row counts that make a « why is it full » answer possible.Values are
unknownon both ends: preferences are integrator-defined, so the core stores them without asserting a shape it does not own.