@hashrytech/quick-components-kit 0.19.11 → 0.19.13

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @hashrytech/quick-components-kit
 
+## 0.19.13
+
+### Patch Changes
+
+- fix: Fixing problem details return
+
+## 0.19.12
+
+### Patch Changes
+
+- fix: Adjusting 2 error handlers so that 1 returns problem details and the other returns the default error
+
 ## 0.19.11
 
 ### Patch Changes

package/dist/modules/fetch-client.d.ts

@@ -65,7 +65,7 @@ export declare class FetchError extends Error {
 export interface FetchClientEvents {
     onRequest?: (request: Request) => Promise<void> | void;
     onResponse?: (response: Response) => Promise<void> | void;
-    onError?: (error: Error) => Promise<void> | void;
+    onError?: (error: ProblemDetail) => Promise<void> | void;
 }
 /**
  * A generic REST API client.

package/dist/modules/fetch-client.js

@@ -1,6 +1,6 @@
 // src/lib/api/client.ts
 import { redirect } from "@sveltejs/kit";
-import { getProblemDetail } from "./problem-details.js";
+import { getProblemDetail, isProblemDetail } from "./problem-details.js";
 import { browser } from "$app/environment";
 /**
  * Custom error class for API responses.
@@ -279,20 +279,17 @@ export class FetchClient {
         catch (error) {
             if (this.debug)
                 console.debug(`Fetch Client: Error occurred while processing request to ${endpoint} with method ${method}`, error);
-            const err = error instanceof Error ? error : new Error(String(error));
-            await this.emit('onError', err);
-            //this.events.onError?.(err);
+            await this.handleError(error);
             const isApiError = error instanceof FetchError;
             const status = isApiError ? error.status : 503; // Service Unavailable fallback
             const message = error instanceof Error ? error.message : 'Unexpected error occurred';
-            const errorObj = isApiError && error.json ? error.json : getProblemDetail({ status, title: "Server fetch error", type: "/exceptions/fetch-error/", detail: message });
-            await this.handleError(errorObj);
-            //const errorObj = status != 503 ? message : getProblemDetail({status, title: "Server fetch error", type: "/exceptions/fetch-error/", detail: "Error fetching data from API", server: message });
-            this.evaluateRedirect(errorObj, status);
+            const problemError = isApiError && error.json && isProblemDetail(error.json) ? error.json : getProblemDetail({ status, title: "Server fetch error", type: "/exceptions/fetch-error/", detail: message });
+            await this.emit('onError', problemError);
+            this.evaluateRedirect(problemError, status);
             return {
                 ok: false,
                 status,
-                error: errorObj
+                error: problemError
             };
         }
     }

package/dist/modules/problem-details.d.ts

@@ -60,3 +60,22 @@ export declare function getProblemDetail(input: {
     type?: string;
     [key: string]: string | number | undefined;
 }): ProblemDetail;
+/**
+ * Type guard for RFC 7807 "Problem Details" objects.
+ *
+ * Why:
+ * - Network errors and server responses can be `unknown` at the callsite.
+ * - This guard lets TypeScript safely narrow `unknown` to `ProblemDetail`
+ *   so you can access `title`, `status`, etc. without extra checks.
+ *
+ * Contract (RFC 7807):
+ * - `title`: human-readable summary (required string)
+ * - `status`: HTTP status code (required number)
+ * - `type`, `detail`, `instance`: optional strings
+ * - Implementations may include arbitrary extension members (we allow them).
+ *
+ * Note:
+ * - Some backends serialize `status` as a string. If that happens in your stack,
+ *   consider accepting `"number-like"` values or coercing before validation.
+*/
+export declare function isProblemDetail(v: unknown): v is ProblemDetail;

package/dist/modules/problem-details.js

@@ -78,3 +78,36 @@ export function getProblemDetail(input) {
     }
     return problem;
 }
+/**
+ * Type guard for RFC 7807 "Problem Details" objects.
+ *
+ * Why:
+ * - Network errors and server responses can be `unknown` at the callsite.
+ * - This guard lets TypeScript safely narrow `unknown` to `ProblemDetail`
+ *   so you can access `title`, `status`, etc. without extra checks.
+ *
+ * Contract (RFC 7807):
+ * - `title`: human-readable summary (required string)
+ * - `status`: HTTP status code (required number)
+ * - `type`, `detail`, `instance`: optional strings
+ * - Implementations may include arbitrary extension members (we allow them).
+ *
+ * Note:
+ * - Some backends serialize `status` as a string. If that happens in your stack,
+ *   consider accepting `"number-like"` values or coercing before validation.
+*/
+export function isProblemDetail(v) {
+    // Must be a non-null object
+    if (!v || typeof v !== 'object')
+        return false;
+    // Treat as a generic dictionary to inspect fields at runtime
+    const o = v;
+    // Required members with exact types
+    const hasTitle = typeof o.title === 'string';
+    const hasStatus = typeof o.status === 'number';
+    // Optional RFC 7807 members (if present, must be strings)
+    const typeOk = o.type === undefined || typeof o.type === 'string';
+    const detailOk = o.detail === undefined || typeof o.detail === 'string';
+    const instanceOk = o.instance === undefined || typeof o.instance === 'string';
+    return hasTitle && hasStatus && typeOk && detailOk && instanceOk;
+}

package/package.json

@@ -5,7 +5,7 @@
     "type": "git",
     "url": "git+https://github.com/hashrytech/quick-components-kit.git"
   },
-  "version": "0.19.11",
+  "version": "0.19.13",
   "license": "MIT",
   "author": "Hashry Tech",
   "files": [