@tumbaland/frontend-core 1.1.1 → 1.2.0

package/dist/apiClient.d.ts

@@ -7,6 +7,8 @@ export interface ApiClientOptions {
 export interface ApiRequestOptions extends RequestInit {
     /** Skip the onUnauthorized callback for this call (e.g. an auth-check that expects 401 as a normal "not logged in" result, not a hard redirect). */
     skipAuthRedirect?: boolean;
+    /** Serialized onto the URL as a query string; undefined/null values are omitted. */
+    params?: Record<string, string | number | boolean | undefined | null>;
 }
 export declare class ApiError extends Error {
     status: number;
@@ -18,9 +20,7 @@ export declare class ApiError extends Error {
  * correlation/session headers, structured errors, and an opt-in 401 →
  * redirect-to-auth hook, per TECHNICAL_REVIEW.md P1.3. `authService` and
  * `groupService` don't route through this: they use different auth
- * transports (cookie vs. Bearer token) that predate this client. New
- * call sites (the many per-front album/finance/etc. service files that
- * still hand-roll fetch) can adopt this incrementally.
+ * transports (cookie vs. Bearer token) that predate this client.
  */
 export declare function createApiClient(options: ApiClientOptions): {
     request: <T = unknown>(path: string, init?: ApiRequestOptions) => Promise<T>;

package/dist/apiClient.js

@@ -1,4 +1,18 @@
 import { getCorrelationId, getSessionId } from '@tumbaland/components';
+function appendParams(path, params) {
+    if (!params)
+        return path;
+    const searchParams = new URLSearchParams();
+    Object.entries(params).forEach(([key, value]) => {
+        if (value !== undefined && value !== null) {
+            searchParams.append(key, String(value));
+        }
+    });
+    const query = searchParams.toString();
+    if (!query)
+        return path;
+    return `${path}${path.includes('?') ? '&' : '?'}${query}`;
+}
 export class ApiError extends Error {
     constructor(status, message, body) {
         super(message);
@@ -12,14 +26,12 @@ export class ApiError extends Error {
  * correlation/session headers, structured errors, and an opt-in 401 →
  * redirect-to-auth hook, per TECHNICAL_REVIEW.md P1.3. `authService` and
  * `groupService` don't route through this: they use different auth
- * transports (cookie vs. Bearer token) that predate this client. New
- * call sites (the many per-front album/finance/etc. service files that
- * still hand-roll fetch) can adopt this incrementally.
+ * transports (cookie vs. Bearer token) that predate this client.
  */
 export function createApiClient(options) {
     async function request(path, init = {}) {
-        const { skipAuthRedirect, headers, ...rest } = init;
-        const response = await fetch(`${options.baseUrl()}${path}`, {
+        const { skipAuthRedirect, headers, params, ...rest } = init;
+        const response = await fetch(`${options.baseUrl()}${appendParams(path, params)}`, {
             credentials: 'include',
             ...rest,
             headers: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tumbaland/frontend-core",
-  "version": "1.1.1",
+  "version": "1.2.0",
   "description": "Shared frontend auth/group/API-client logic for Tumbaland frontends",
   "author": "Tumbaland",
   "license": "MIT",