@envelop/response-cache-cloudflare-kv/esm/set.js

- Supports [Cloudflare KV](https://developers.cloudflare.com/kv/) cache for `@envelop/response-cache` plugin - Suitable for graphql servers running on [Cloudflare Workers](https://workers.cloudflare.com/)

import { buildEntityKey, buildOperationKey } from './cache-key.js';
export function set(
/** id/hash of the operation */
id, 
/** the result that should be cached */
data, 
/** array of entity records that were collected during execution */
entities, 
/** how long the operation should be cached (in milliseconds) */
ttl, KV, keyPrefix) {
    const ttlInSeconds = Math.max(Math.floor(ttl / 1000), 60); // KV TTL must be at least 60 seconds
    const operationKey = buildOperationKey(id, keyPrefix);
    const operationKeyWithoutPrefix = buildOperationKey(id);
    const kvPromises = []; // Collecting all the KV operations so we can await them all at once
    kvPromises.push(KV.put(operationKey, JSON.stringify(data), {
        expirationTtl: ttlInSeconds,
        metadata: { operationKey },
    }));
    // Store connections between the entities and the operation key
    // E.g if the entities are User:1 and User:2, we need to know that the operation key is connected to both of them
    for (const entity of entities) {
        const entityKey = buildEntityKey(entity.typename, entity.id, keyPrefix);
        kvPromises.push(KV.put(`${entityKey}:${operationKeyWithoutPrefix}`, operationKey, {
            expirationTtl: ttlInSeconds,
            metadata: { operationKey },
        }));
    }
    return Promise.allSettled(kvPromises).then(() => undefined);
}