@managemint-solutions/sdk 0.37.0 → 0.38.1

package/dist/transforms.js

@@ -3,7 +3,7 @@
 // select strings and their list results.
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.restoredPatch = exports.deletedPatch = exports.unarchivedPatch = exports.archivedPatch = exports.toMmsList = exports.USER_PROFILE_EMBED = exports.toDateInput = exports.orIlike = exports.ilikeContains = exports.parseEntityIdFilter = void 0;
-// v7, to match the `mms_id` columns these filters compare against — `public.uuidv7()` is the
+// v7, to match the `mms_id` columns these filters compare against - `public.uuidv7()` is the
 // default on every table. This is the gate in front of `@IsUUID('7')`, so a stricter version
 // here would null the id out before validation ever saw it, and a looser one would let a value
 // through that the DTO then rejects.
@@ -11,7 +11,7 @@ const UUID_V7 = /^[0-9a-f]{8}-[0-9a-f]{4}-7[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f
 /**
  * The `client_id` / `project_id` list filters accept either a plain UUID v7 or the base64-JSON
  * option value the portal's selects send (`{ mms_id }`, or `{ id }` as a fallback). Anything that
- * is not one of those — including a value that decodes to JSON without a UUID v7 — cannot filter
+ * is not one of those - including a value that decodes to JSON without a UUID v7 - cannot filter
  * anything, so it becomes `null` and the filter is skipped.
  */
 const parseEntityIdFilter = (value) => {
@@ -35,19 +35,19 @@ exports.parseEntityIdFilter = parseEntityIdFilter;
 /**
  * A `%value%` ilike pattern, double-quoted for PostgREST's `or=(...)` grammar so `,`, `(`, `)`,
  * `.`, `"` and `\` in the search stay literal instead of being read as more filters. Inside the
- * quotes only `"` and `\` need escaping, which is what PostgREST defines — the `\,` the list
+ * quotes only `"` and `\` need escaping, which is what PostgREST defines - the `\,` the list
  * endpoints used to emit was never an escape at all. LIKE's own wildcards `%` and `_` are left
  * alone and still match as wildcards; they only widen the caller's own search, never its scope.
  */
 const ilikeContains = (value) => `"%${value.replace(/[\\"]/g, '\\$&')}%"`;
 exports.ilikeContains = ilikeContains;
-/** The `or=(...)` argument matching `search` against any of `columns` — `name.ilike."%x%",…`. */
+/** The `or=(...)` argument matching `search` against any of `columns` - `name.ilike."%x%",…`. */
 const orIlike = (columns, search) => columns.map((column) => `${column}.ilike.${(0, exports.ilikeContains)(search)}`).join(',');
 exports.orIlike = orIlike;
 /**
  * `date` columns take an ISO string. The shared `CreateProjectDto`/`UpdateProjectDto` types
- * declare `Date`, but over the wire the value is the validated `@IsDateString` string — which
- * must reach Postgres byte-identical ('2026-04-22' is a plain date, not an instant) — so only a
+ * declare `Date`, but over the wire the value is the validated `@IsDateString` string - which
+ * must reach Postgres byte-identical ('2026-04-22' is a plain date, not an instant) - so only a
  * real `Date` (a portal caller) is serialized.
  */
 const toDateInput = (value) => value instanceof Date ? value.toISOString() : value;
@@ -66,7 +66,7 @@ exports.USER_PROFILE_EMBED = `(
         )`;
 /**
  * The `MmsList` envelope every paginated read returns. `rows` is `unknown` because each select
- * string produces its own row shape — the caller's `T` is what declares it. `count` is
+ * string produces its own row shape - the caller's `T` is what declares it. `count` is
  * PostgREST's estimate, so an empty page reports 0 total pages rather than 1.
  */
 const toMmsList = (rows, page, pageSize, count) => {
@@ -85,7 +85,7 @@ const toMmsList = (rows, page, pageSize, count) => {
 exports.toMmsList = toMmsList;
 // The soft archive/delete patches projects, tasks and clients all write: the flag the transition
 // sets, plus the who/when stamps named after it. `unarchived`/`restored` clear the flag their
-// counterpart set and stamp their own columns — the earlier ones stay as the history.
+// counterpart set and stamp their own columns - the earlier ones stay as the history.
 const archivedPatch = (by) => ({
     archived: true,
     archived_at: new Date().toISOString(),

package/dist/users/dto.d.ts

@@ -16,7 +16,7 @@ export declare class AddUserDto implements CreateUserDtoType {
      * Optional: an internally created user - the owner at signup - has no client
      * request behind it, and one is generated for it.
      *
-     * Still v4: the key is not an `mms_id` — the column is `text` — and the api fills a missing
+     * Still v4: the key is not an `mms_id` - the column is `text` - and the api fills a missing
      * one with `randomUUID()`, which is v4.
      */
     readonly idempotency_key?: string;
@@ -50,13 +50,13 @@ export declare class UpdateUserDto implements UpdateUserDtoType {
     readonly emergency_contact_email?: string | null;
 }
 /**
- * `PATCH /users/me` — what a member may change about themselves.
+ * `PATCH /users/me` - what a member may change about themselves.
  *
  * Every field here also appears on UpdateUserDto with the same constraints; what makes
  * this a separate class is what it *omits*. The api's ValidationPipe runs
  * `whitelist + forbidNonWhitelisted`, so a self-service request carrying `job_title`,
  * `manager_id`, `employment_type`, `start_date`, `end_date` or `profile_image` is
- * rejected with a 400 rather than silently ignored — the narrowing is the guard.
+ * rejected with a 400 rather than silently ignored - the narrowing is the guard.
  */
 export declare class UpdateMyProfileDto implements UpdateMyProfileDtoType {
     readonly name: string;

package/dist/users/dto.js

@@ -38,7 +38,7 @@ class AddUserDto {
      * Optional: an internally created user - the owner at signup - has no client
      * request behind it, and one is generated for it.
      *
-     * Still v4: the key is not an `mms_id` — the column is `text` — and the api fills a missing
+     * Still v4: the key is not an `mms_id` - the column is `text` - and the api fills a missing
      * one with `randomUUID()`, which is v4.
      */
     idempotency_key;
@@ -87,7 +87,7 @@ __decorate([
     __metadata("design:type", String)
 ], AddUserDto.prototype, "idempotency_key", void 0);
 // `active_in` arrives as a CSV string and is transformed to booleans, so it is omitted from the
-// implemented contract — the same exception GetClientsDto makes for status_id_in.
+// implemented contract - the same exception GetClientsDto makes for status_id_in.
 class GetUsersQueryDto {
     search;
     page = 1;
@@ -284,13 +284,13 @@ __decorate([
     __metadata("design:type", Object)
 ], UpdateUserDto.prototype, "emergency_contact_email", void 0);
 /**
- * `PATCH /users/me` — what a member may change about themselves.
+ * `PATCH /users/me` - what a member may change about themselves.
  *
  * Every field here also appears on UpdateUserDto with the same constraints; what makes
  * this a separate class is what it *omits*. The api's ValidationPipe runs
  * `whitelist + forbidNonWhitelisted`, so a self-service request carrying `job_title`,
  * `manager_id`, `employment_type`, `start_date`, `end_date` or `profile_image` is
- * rejected with a 400 rather than silently ignored — the narrowing is the guard.
+ * rejected with a 400 rather than silently ignored - the narrowing is the guard.
  */
 class UpdateMyProfileDto {
     name;

package/dist/users/index.d.ts

@@ -23,7 +23,7 @@ export declare class UsersResource {
      * The public profile behind a `*_by` / `manager_id` column. `user_profiles` is a
      * `security_invoker = on` view granted to `authenticated` (the base table's tenant predicate
      * scopes it), so this runs on the caller's own
-     * client — it needs no service role.
+     * client - it needs no service role.
      */
     identityById(userId?: string | null): Promise<UserIdentity | null>;
     /** The users who report to `managerId` - the direct reports a leave approver may act on. */
@@ -41,7 +41,7 @@ export declare class UsersResource {
      * avatar change is audited like any other.
      *
      * The previous object is removed *after* the new URL is committed, and a failed cleanup is
-     * swallowed — an orphaned object is a storage bill, a failed upload is a broken avatar.
+     * swallowed - an orphaned object is a storage bill, a failed upload is a broken avatar.
      */
     setProfileImage(userId: string, file: File): Promise<UserRow>;
     /**

package/dist/users/index.js

@@ -78,7 +78,7 @@ class UsersResource {
      * The public profile behind a `*_by` / `manager_id` column. `user_profiles` is a
      * `security_invoker = on` view granted to `authenticated` (the base table's tenant predicate
      * scopes it), so this runs on the caller's own
-     * client — it needs no service role.
+     * client - it needs no service role.
      */
     async identityById(userId) {
         if (!userId)
@@ -142,7 +142,7 @@ class UsersResource {
      * avatar change is audited like any other.
      *
      * The previous object is removed *after* the new URL is committed, and a failed cleanup is
-     * swallowed — an orphaned object is a storage bill, a failed upload is a broken avatar.
+     * swallowed - an orphaned object is a storage bill, a failed upload is a broken avatar.
      */
     async setProfileImage(userId, file) {
         const { name, extension } = (0, paths_1.splitFileName)((0, paths_1.sanitizeFileName)(file.name));

package/dist/users/paths.d.ts

@@ -3,7 +3,7 @@ export declare const PROFILE_PICTURES_BUCKET = "profile-pictures";
 /**
  * Where a member's avatar lives in the `profile-pictures` bucket.
  *
- * `organizationId/userId/timestamp-file` — the organization leads so the storage policy can
+ * `organizationId/userId/timestamp-file` - the organization leads so the storage policy can
  * scope by tenant, and the user id follows so it can scope by owner. Neither segment comes
  * from the client.
  *
@@ -17,7 +17,7 @@ export declare const profileImagePath: (organizationId: string, userId: string,
  * The object key behind a stored `users.profile_image` URL, so the previous avatar can be
  * removed when a new one replaces it.
  *
- * Returns null for anything that is not one of our own public URLs — the column also holds
+ * Returns null for anything that is not one of our own public URLs - the column also holds
  * whatever `raw_user_meta_data` carried at signup (a Google or Gravatar URL), and those are
  * not ours to delete.
  */

package/dist/users/paths.js

@@ -6,7 +6,7 @@ exports.PROFILE_PICTURES_BUCKET = 'profile-pictures';
 /**
  * Where a member's avatar lives in the `profile-pictures` bucket.
  *
- * `organizationId/userId/timestamp-file` — the organization leads so the storage policy can
+ * `organizationId/userId/timestamp-file` - the organization leads so the storage policy can
  * scope by tenant, and the user id follows so it can scope by owner. Neither segment comes
  * from the client.
  *
@@ -21,7 +21,7 @@ exports.profileImagePath = profileImagePath;
  * The object key behind a stored `users.profile_image` URL, so the previous avatar can be
  * removed when a new one replaces it.
  *
- * Returns null for anything that is not one of our own public URLs — the column also holds
+ * Returns null for anything that is not one of our own public URLs - the column also holds
  * whatever `raw_user_meta_data` carried at signup (a Google or Gravatar URL), and those are
  * not ours to delete.
  */

package/dist/webhook-events/index.d.ts

@@ -17,7 +17,7 @@ export type ClaimOutcome = {
     kind: 'vanished';
 };
 /**
- * The provider event logs — `paystack_webhook_events` and `resend_webhook_events`. Every policy
+ * The provider event logs - `paystack_webhook_events` and `resend_webhook_events`. Every policy
  * on both is `false` for `authenticated`, including READ: the raw payloads are never exposed to
  * end users, and an inbound webhook has no caller to run as.
  *
@@ -30,7 +30,7 @@ export declare class WebhookEventsResource {
     private readonly table;
     constructor(supabase: TypedSupabaseClient, table: WebhookEventsTable);
     /**
-     * The dedup test. One insert, straight to `processing` — there is no useful window in which
+     * The dedup test. One insert, straight to `processing` - there is no useful window in which
      * the row would sit at `received`.
      *
      * The unique index is partial (`where processing_status <> 'ignored_duplicate'`), so at
@@ -44,7 +44,7 @@ export declare class WebhookEventsResource {
     findByEventKey(eventKey: string): Promise<WebhookEventRow | null>;
     /**
      * Reclaims a `failed` row for reprocessing, clearing the previous failure. Guarded on the
-     * row still being failed, because another redelivery may have reclaimed it first — resolves
+     * row still being failed, because another redelivery may have reclaimed it first - resolves
      * to null when it did.
      *
      * This is the single most important detail in the pipeline: swallowing a redelivery of a

package/dist/webhook-events/index.js

@@ -4,7 +4,7 @@ exports.WebhookEventsResource = void 0;
 const errors_1 = require("../errors");
 const UNIQUE_VIOLATION = '23505';
 /**
- * The provider event logs — `paystack_webhook_events` and `resend_webhook_events`. Every policy
+ * The provider event logs - `paystack_webhook_events` and `resend_webhook_events`. Every policy
  * on both is `false` for `authenticated`, including READ: the raw payloads are never exposed to
  * end users, and an inbound webhook has no caller to run as.
  *
@@ -20,7 +20,7 @@ class WebhookEventsResource {
         this.table = table;
     }
     /**
-     * The dedup test. One insert, straight to `processing` — there is no useful window in which
+     * The dedup test. One insert, straight to `processing` - there is no useful window in which
      * the row would sit at `received`.
      *
      * The unique index is partial (`where processing_status <> 'ignored_duplicate'`), so at
@@ -57,7 +57,7 @@ class WebhookEventsResource {
     }
     /**
      * Reclaims a `failed` row for reprocessing, clearing the previous failure. Guarded on the
-     * row still being failed, because another redelivery may have reclaimed it first — resolves
+     * row still being failed, because another redelivery may have reclaimed it first - resolves
      * to null when it did.
      *
      * This is the single most important detail in the pipeline: swallowing a redelivery of a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@managemint-solutions/sdk",
-  "version": "0.37.0",
+  "version": "0.38.1",
   "description": "Typed Supabase data-access SDK for ManageMint Solutions",
   "license": "UNLICENSED",
   "author": "Scott Bebington <scottbebington@gmail.com>",
@@ -51,7 +51,7 @@
     "testEnvironment": "node"
   },
   "dependencies": {
-    "@managemint-solutions/entities": "^1.21.0"
+    "@managemint-solutions/entities": "^1.22.0"
   },
   "peerDependencies": {
     "@nestjs/common": "^11.0.0",