@managemint-solutions/entities 1.18.0 → 1.20.0

package/dist/feature-flags/index.d.ts

@@ -4,6 +4,13 @@ import type { ConfigEntity } from '../configs';
  * it in Supabase Studio; the api reads it by this name and caches the value for a day.
  */
 export declare const FEATURE_FLAGS_CONFIG_NAME = "portal_feature_flags";
+/**
+ * The Redis entry the api writes the flags to, and the portal reads first - the same
+ * entry, so one write serves both. Bump the version when the wire shape changes; old
+ * entries simply stop matching.
+ */
+export declare const FEATURE_FLAGS_CACHE_VERSION = "v1";
+export declare const FEATURE_FLAGS_CACHE_KEY = "config:v1:portal_feature_flags";
 /**
  * One flag's rule: `true` for everyone, `false` for no one, or on only for the listed
  * emails. Anything else - a missing flag, a malformed rule - is read as off by the portal.

package/dist/feature-flags/index.js

@@ -1,8 +1,15 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.FEATURE_FLAGS_CONFIG_NAME = void 0;
+exports.FEATURE_FLAGS_CACHE_KEY = exports.FEATURE_FLAGS_CACHE_VERSION = exports.FEATURE_FLAGS_CONFIG_NAME = void 0;
 /**
  * The row of `public.configs` that holds the portal's feature flags. Scott creates and edits
  * it in Supabase Studio; the api reads it by this name and caches the value for a day.
  */
 exports.FEATURE_FLAGS_CONFIG_NAME = 'portal_feature_flags';
+/**
+ * The Redis entry the api writes the flags to, and the portal reads first - the same
+ * entry, so one write serves both. Bump the version when the wire shape changes; old
+ * entries simply stop matching.
+ */
+exports.FEATURE_FLAGS_CACHE_VERSION = 'v1';
+exports.FEATURE_FLAGS_CACHE_KEY = `config:${exports.FEATURE_FLAGS_CACHE_VERSION}:${exports.FEATURE_FLAGS_CONFIG_NAME}`;

package/dist/users/cache/index.d.ts

@@ -1,20 +1,19 @@
 /**
- * The contract for the portal's edge cache of each member's own `GET /users/me`.
+ * The contract for the portal's Redis cache of each member's own `GET /users/me`.
  *
- * The portal owns the cache (Upstash Redis through the sdk cache subpath, one entry per
- * member, written on a miss); the api never reads it and only invalidates tags after a write. Both sides import
- * these so a change to the shape or the tagging is one edit.
+ * One hash per organization, `profiles:v1:<organization_id>`, with one field per member
+ * named by their `mms_id` and holding their `LoggedInUser`. The portal writes a field on a
+ * miss; the api never reads the hash and only deletes a field (a member's write) or the
+ * whole hash (a write that changes every member's profile). Both sides build the key from
+ * these constants - the builder itself lives in `@managemint-solutions/sdk/cache`.
  */
-/** Bump when the LoggedInUser wire shape changes; old entries simply stop matching. */
-export declare const USER_ME_CACHE_VERSION = "v1";
-/** The hard ceiling on how stale a cached profile may be, in seconds (one day). */
-export declare const USER_ME_CACHE_TTL_SECONDS = 86400;
-/** The cache key of one member's LoggedInUser blob. Portal-internal; versioned here. */
-export declare const userMeCacheKey: (mmsId: string) => string;
-/** Expiring this tag drops one member's blob - every write to that member's row or permissions. */
-export declare const userCacheTag: (mmsId: string) => string;
+/** Bump when the LoggedInUser wire shape changes; old hashes simply stop matching. */
+export declare const PROFILE_CACHE_VERSION = "v1";
+/** The hash key is this prefix followed by the organization's `mms_id`. */
+export declare const PROFILE_CACHE_KEY_PREFIX = "profiles:v1:";
 /**
- * Expiring this tag drops every member's blob in the organization - a write that changes
- * what all of them see (the module set folded into their permissions).
+ * The hard ceiling on how stale a cached profile may be, in seconds (one day). Set once,
+ * when a hash is first written, so an organization's whole cache re-reads once a day
+ * however busy it is.
  */
-export declare const organizationCacheTag: (organizationId: string) => string;
+export declare const PROFILE_CACHE_TTL_SECONDS = 86400;

package/dist/users/cache/index.js

@@ -1,26 +1,22 @@
 "use strict";
 /**
- * The contract for the portal's edge cache of each member's own `GET /users/me`.
+ * The contract for the portal's Redis cache of each member's own `GET /users/me`.
  *
- * The portal owns the cache (Upstash Redis through the sdk cache subpath, one entry per
- * member, written on a miss); the api never reads it and only invalidates tags after a write. Both sides import
- * these so a change to the shape or the tagging is one edit.
+ * One hash per organization, `profiles:v1:<organization_id>`, with one field per member
+ * named by their `mms_id` and holding their `LoggedInUser`. The portal writes a field on a
+ * miss; the api never reads the hash and only deletes a field (a member's write) or the
+ * whole hash (a write that changes every member's profile). Both sides build the key from
+ * these constants - the builder itself lives in `@managemint-solutions/sdk/cache`.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.organizationCacheTag = exports.userCacheTag = exports.userMeCacheKey = exports.USER_ME_CACHE_TTL_SECONDS = exports.USER_ME_CACHE_VERSION = void 0;
-/** Bump when the LoggedInUser wire shape changes; old entries simply stop matching. */
-exports.USER_ME_CACHE_VERSION = 'v1';
-/** The hard ceiling on how stale a cached profile may be, in seconds (one day). */
-exports.USER_ME_CACHE_TTL_SECONDS = 86400;
-/** The cache key of one member's LoggedInUser blob. Portal-internal; versioned here. */
-const userMeCacheKey = (mmsId) => `user:me:${exports.USER_ME_CACHE_VERSION}:${mmsId}`;
-exports.userMeCacheKey = userMeCacheKey;
-/** Expiring this tag drops one member's blob - every write to that member's row or permissions. */
-const userCacheTag = (mmsId) => `user:${mmsId}`;
-exports.userCacheTag = userCacheTag;
+exports.PROFILE_CACHE_TTL_SECONDS = exports.PROFILE_CACHE_KEY_PREFIX = exports.PROFILE_CACHE_VERSION = void 0;
+/** Bump when the LoggedInUser wire shape changes; old hashes simply stop matching. */
+exports.PROFILE_CACHE_VERSION = 'v1';
+/** The hash key is this prefix followed by the organization's `mms_id`. */
+exports.PROFILE_CACHE_KEY_PREFIX = `profiles:${exports.PROFILE_CACHE_VERSION}:`;
 /**
- * Expiring this tag drops every member's blob in the organization - a write that changes
- * what all of them see (the module set folded into their permissions).
+ * The hard ceiling on how stale a cached profile may be, in seconds (one day). Set once,
+ * when a hash is first written, so an organization's whole cache re-reads once a day
+ * however busy it is.
  */
-const organizationCacheTag = (organizationId) => `org:${organizationId}`;
-exports.organizationCacheTag = organizationCacheTag;
+exports.PROFILE_CACHE_TTL_SECONDS = 86400;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@managemint-solutions/entities",
-  "version": "1.18.0",
+  "version": "1.20.0",
   "description": "Entity types used by both the api and portal",
   "homepage": "https://github.com/ManageMint-Solutions/managemint-solutions-entities#readme",
   "bugs": {