Optional
cache?: CacheSetting"no-store"
Optional
responseDue to the nature of dynamic and custom data, it is possible to write data to redis that is not valid json and will therefore cause errors when deserializing. This used to happen very frequently with non-utf8 data, such as emojis.
By default we will therefore encode the data as base64 on the server, before sending it to the client. The client will then decode the base64 data and parse it as utf8.
For very large entries, this can add a few milliseconds, so if you are sure that your data is valid utf8, you can disable this behaviour by setting this option to false.
Here's what the response body looks like:
{
result?: "base64-encoded",
error?: string
}
"base64"
Optional
retry?: RetryConfigConfigure the retry behaviour in case of network errors
Configure the cache behaviour