@iblai/data-layer 1.27.0 → 1.29.0

package/dist/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iblai/data-layer",
-  "version": "1.26.0",
+  "version": "1.28.0",
   "description": "ibl.ai data layer",
   "main": "dist/index.esm.js",
   "types": "dist/index.d.ts",

package/dist/src/features/chat-privacy/api-slice.d.ts

@@ -24,11 +24,32 @@ export interface UserChatPrivacySettings {
     chat_privacy_enabled: boolean;
     chat_privacy_mode: ChatPrivacyMode | null;
 }
+/**
+ * `is_locked` is true only when the winning tier is `mentor` or `tenant`. A
+ * mentor with `disable_privacy_mode` on therefore reports `is_locked: true`
+ * only when it actually clamped a user's global "disabled" preference to
+ * `anonymized`; for everyone else the read says `normal` / `default` /
+ * unlocked, so the lock itself has to be read from the mentor's public
+ * settings (`MentorChatPrivacyPublicSettings`).
+ */
 export interface ChatPrivacyEffective {
     mode: ChatPrivacyMode;
     source: 'tenant' | 'mentor' | 'user' | 'session' | 'default';
     is_locked: boolean;
 }
+/**
+ * Chat-privacy fields of `GET …/mentors/{mentor}/public-settings/` — readable
+ * by members, writable through the mentor settings PUT by admins only.
+ */
+export interface MentorChatPrivacyPublicSettings {
+    /**
+     * When on, end users cannot make conversations with this mentor private:
+     * the SPA hides the privacy toggle, and the backend answers a private
+     * session start or a `disable-chathistory` flip with 403. `null` is an
+     * older record and means off.
+     */
+    disable_privacy_mode?: boolean | null;
+}
 interface OrgUserArgs {
     org: string;
     userId: string;

package/dist/src/features/return-base-query-errors.d.ts

@@ -0,0 +1,25 @@
+import type { BaseQueryFn } from '@reduxjs/toolkit/query';
+type AnyBaseQuery = BaseQueryFn<any, any, any, any, any>;
+/**
+ * Makes a base query that reports failures by THROWING report them by
+ * RETURNING `{ error }` instead, which is the only form RTK Query keeps.
+ *
+ * `iblFetchBaseQuery` throws `{ status, data }` on any failed request. RTK
+ * Query treats a thrown value as an unhandled exception: the thunk rejects
+ * with `miniSerializeError(e)`, which copies only `name` / `message` /
+ * `stack` / `code`. For a `{ status, data }` object that leaves `{}` — so
+ * `.unwrap()` rejects with an empty object and a hook's `error` is empty too.
+ * The HTTP status and the backend's body never reach the caller: a 403 cannot
+ * be told from any other failure, and a 400's field messages or its
+ * form-level `error` string cannot be shown.
+ *
+ * Wrap a slice's base query with this when its callers need the status or the
+ * body, e.g. to place backend validation messages next to their fields.
+ *
+ * Only values that look like an RTK error (an object with a `status`) are
+ * converted; anything else is rethrown untouched. Note that a returned error
+ * also lets a mutation's static `invalidatesTags` run, as RTK does for any
+ * handled error.
+ */
+export declare function withReturnedErrors<Query extends AnyBaseQuery>(baseQuery: Query): Query;
+export {};

package/dist/tests/features/chat-privacy/api-slice.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/tests/features/return-base-query-errors.test.d.ts

@@ -0,0 +1 @@
+export {};