localForage is a great way to make sure that you've got the most persistent localStorage available on the device and webview that you are using, but operations (like replacing a keyValue) can be tedious, and our approach of multi-op currying makes it very flexible. It is written and tested in typescript, and ships with commonjs and an ejs versions - as well as all of its own typings in case you are using typescript.
If you don't know how localForage works, you would do well to check out those docs - because that is the underlying engine that this library uses. But for a refresher, localForage uses IndexedDB, WebSQL, or localStorage - depending on the best engine that the browser offers.
Install with your package manager
yarn add @tauri-apps/tauri-forage
Import into your JS / TS
import { forage } from '@tauri-apps/tauri-forage'
Use it:
forage.setItem({
key: 'yourKey',
value: 'a value'
})()
Here is the getItem
function. There is a lot to discuss, and once you've understood the principle all of the other functions will make sense to you. If you want to see more details, check out the tests in test/__tests__/tauriForage.spec.ts
getItem ({ key, logger, returner, before, store }: BeforeItem = {}) {
return async function (curry?: MaybeFunction) {
const storage = await _defineStore({ store: store })
key = before ? await handler.maybeCurry(curry || null)(key) : key
return handler.returner(
storage.getItem(key).then(async (v: any) => {
return !before ? handler.maybeCurry(curry || null)(v) : v
}).catch((err: any) => {
/* istanbul ignore next */
return handler.logger(err, logger)
})
)(returner)
}
}
In its most simple incarnation, you can just get the keyValue of the keyName.
You can instruct every function to return the value in specific ways.
If an error occurs, you can determine how to respond:
If you want, you can also use these handler functions yourself! They are properly exported and typed!
However you can also curry the returned value with a function you can pass into the function call.
Let's look at a few tests to see how currying can be applied:
it('will curry after', async () => {
await forage.setItem({
key: 'user',
value: { name: 'Alice' }
} as any)()
const curry = (v: any) => v.toUpperCase()
const user = await forage.getKeyValue({
key: 'user',
value: 'name'
} as any)(curry)
expect(user).toStrictEqual('ALICE')
})
You can also curry the value BEFORE it is used by localForage. This example is obviously quite trivial, but you may start to see a pattern emerge.
it('will curry before', async () => {
// you can set objects or arrays or even huge base64 strings for values
await forage.setItem({
key: 'user',
value: {
name: 'Alice'
}
} as any)()
const curry = (v: any) => v.toLowerCase()
const user = await forage.getKeyValue({
key: 'user',
value: 'NAME',
before: true
} as any)(curry)
expect(user).toStrictEqual('Alice')
})
If you want to have multiple "stores", you can easily do that too.
Of note are the extensions to the generic interface:
Even if undefined is saved, null will be returned by getItem(). This is due to a limitation in localStorage, and for compatibility reasons localForage cannot store the value undefined.
Tests are written with Jasmine flavor using Jest.
The docs are available as a static site in /docs
(c) 2019-2020 - Daniel Thompson-Yvetot and contributors
MIT