@iblai/data-layer 1.27.0 → 1.28.0

package/dist/index.js

@@ -42256,9 +42256,51 @@ const credentialsApiSlice = react.createApi({
 });
 const { useGetCredentialsQuery, useLazyGetCredentialsQuery, useGetUserCredentialsQuery, useLazyGetUserCredentialsQuery, useCreateCallCredentialsMutation, useGetIntegrationCredentialsQuery, useLazyGetIntegrationCredentialsQuery, useCreateIntegrationCredentialMutation, useUpdateIntegrationCredentialMutation, useGetLLMCredentialsQuery, useLazyGetLLMCredentialsQuery, useCreateLLMCredentialMutation, useGetConnectedServiceAuthUrlQuery, useLazyGetConnectedServiceAuthUrlQuery, useConnectedServicesCallbackQuery, useLazyConnectedServicesCallbackQuery, useGetUsersAsAssertionsQuery, useLazyGetUsersAsAssertionsQuery, useCreateCredentialAssertionMutation, useGetCredentialsListQuery, useLazyGetCredentialsListQuery, useCreateCredentialMutation, useUpdateCredentialMutation, useDeleteCourseCredentialMutation, useGetProviderConfigQuery, useLazyGetProviderConfigQuery, useCreateProviderConfigMutation, useDeleteProviderConfigMutation, useGetExternalMappingQuery, useLazyGetExternalMappingQuery, useCreateExternalMappingMutation, useDeleteExternalMappingMutation, } = credentialsApiSlice;
 
+/**
+ * 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.
+ */
+function withReturnedErrors(baseQuery) {
+    // Returned as `Query` so a slice keeps the exact argument, error and meta
+    // types of the base query it wraps.
+    const wrapped = async (args, api, extraOptions) => {
+        try {
+            return await baseQuery(args, api, extraOptions);
+        }
+        catch (thrown) {
+            if (typeof thrown === 'object' && thrown !== null && 'status' in thrown) {
+                return { error: thrown };
+            }
+            throw thrown;
+        }
+    };
+    return wrapped;
+}
+
 const chatPrivacyApiSlice = react.createApi({
     reducerPath: 'chatPrivacyApiSlice',
-    baseQuery: iblFetchBaseQuery,
+    // Callers read the failure itself: the 403 a locked mentor answers to a
+    // `disable-chathistory` flip carries its reason in `data.detail`, and the
+    // one-way 400 carries it under the field name. `iblFetchBaseQuery` throws
+    // its errors, which reach `.unwrap()` and the hooks as `{}`.
+    baseQuery: withReturnedErrors(iblFetchBaseQuery),
     tagTypes: ['TenantChatPrivacyConfig', 'UserChatPrivacySettings', 'ChatPrivacyEffective'],
     endpoints: (builder) => ({
         getTenantChatPrivacyConfig: builder.query({