@techfinityedge/koolbase-react-native 3.1.0 → 4.0.0

package/README.md

@@ -257,6 +257,28 @@ const results = await Koolbase.db.batch([
 
 ---
 
+### Handling write conflicts
+
+`insert`, `update`, and `upsert` are online-first: when the server is reachable they throw a typed error on rejection. Catch `KoolbaseConflictError` to handle unique-constraint violations (e.g. a duplicate email):
+
+```ts
+import { KoolbaseConflictError } from '@techfinityedge/koolbase-react-native';
+
+try {
+  await Koolbase.db.insert('users', { email, name });
+} catch (e) {
+  if (e instanceof KoolbaseConflictError) {
+    showError(`That ${e.field ?? 'value'} is already in use.`);
+  } else {
+    throw e;
+  }
+}
+```
+
+When the device is offline, these writes are queued and synced automatically when connectivity returns.
+
+---
+
 ## Storage
 
 ```typescript

package/dist/database-errors.d.ts

@@ -20,10 +20,11 @@ export declare class KoolbaseDataError extends Error {
  * (`details.field`) — useful when a collection has more than one unique
  * constraint and you need to know which value clashed.
  *
- * Currently surfaced by `upsert` (the online-only write). `insert` and
- * `update` are optimistic/offline-first: they accept the write locally and
- * sync in the background, so a constraint conflict on those paths is a
- * sync-time concern rather than a thrown error.
+ * Surfaced by `insert`, `update`, and `upsert` whenever the server is
+ * reachable and rejects the write with a 409. These writes are online-first:
+ * a server-side conflict throws immediately. Only a genuine network failure
+ * falls back to the offline queue, where a conflict that surfaces at sync
+ * time is handled by the sync engine rather than thrown here.
  *
  * @example
  * try {

package/dist/database-errors.js

@@ -29,10 +29,11 @@ exports.KoolbaseDataError = KoolbaseDataError;
  * (`details.field`) — useful when a collection has more than one unique
  * constraint and you need to know which value clashed.
  *
- * Currently surfaced by `upsert` (the online-only write). `insert` and
- * `update` are optimistic/offline-first: they accept the write locally and
- * sync in the background, so a constraint conflict on those paths is a
- * sync-time concern rather than a thrown error.
+ * Surfaced by `insert`, `update`, and `upsert` whenever the server is
+ * reachable and rejects the write with a 409. These writes are online-first:
+ * a server-side conflict throws immediately. Only a genuine network failure
+ * falls back to the offline queue, where a conflict that surfaces at sync
+ * time is handled by the sync engine rather than thrown here.
  *
  * @example
  * try {

package/dist/database.d.ts

@@ -9,6 +9,18 @@ export declare class KoolbaseDatabase {
     private request;
     private runQuery;
     query(collection: string, options?: QueryOptions): Promise<QueryResult>;
+    /**
+     * Insert a new record into a collection.
+     *
+     * Online-first: awaits the server so a server-side rejection (unique
+     * violation, validation error, permission denial) surfaces as the typed
+     * `KoolbaseDataError` subclass — `insert` now throws `KoolbaseConflictError`
+     * with the offending field on a 409, matching `upsert` and `update`.
+     *
+     * On genuine network failure (server unreachable, timeout) the write is
+     * accepted optimistically: saved to the local cache and queued for sync
+     * when connectivity returns.
+     */
     insert(collection: string, data: Record<string, unknown>): Promise<KoolbaseRecord>;
     /**
      * Insert a record, or update the existing one matching `match`.
@@ -63,6 +75,19 @@ export declare class KoolbaseDatabase {
      */
     batch(operations: BatchOp[]): Promise<BatchResult[]>;
     get(recordId: string): Promise<KoolbaseRecord>;
+    /**
+     * Update a record's fields by id.
+     *
+     * Online-first: awaits the server so a server-side rejection (unique
+     * violation, not found, permission denial) surfaces as the typed
+     * `KoolbaseDataError` subclass. An update that would violate a unique
+     * constraint now throws `KoolbaseConflictError` with the offending field —
+     * same shape as `insert` and `upsert`.
+     *
+     * On genuine network failure the update is queued for sync and a partial
+     * optimistic record is returned so the UI can re-render the new fields
+     * immediately.
+     */
     update(recordId: string, data: Record<string, unknown>): Promise<KoolbaseRecord>;
     delete(recordId: string): Promise<void>;
     syncPendingWrites(): Promise<void>;

package/dist/database.js

@@ -84,39 +84,56 @@ class KoolbaseDatabase {
         await (0, cache_store_1.setCached)(userId, collection, queryHash, result);
         return { ...result, isFromCache: false };
     }
-    // ─── Insert (optimistic) ────────────────────────────────────────────────────
+    // ─── Insert (online-first with offline fallback) ───────────────────────────
+    /**
+     * Insert a new record into a collection.
+     *
+     * Online-first: awaits the server so a server-side rejection (unique
+     * violation, validation error, permission denial) surfaces as the typed
+     * `KoolbaseDataError` subclass — `insert` now throws `KoolbaseConflictError`
+     * with the offending field on a 409, matching `upsert` and `update`.
+     *
+     * On genuine network failure (server unreachable, timeout) the write is
+     * accepted optimistically: saved to the local cache and queued for sync
+     * when connectivity returns.
+     */
     async insert(collection, data) {
         const userId = this.getUserId() ?? 'anonymous';
-        // Build optimistic record
-        const optimisticRecord = {
-            id: generateId(),
-            createdBy: userId,
-            data,
-            createdAt: new Date().toISOString(),
-            updatedAt: new Date().toISOString(),
-        };
-        // Write to local cache immediately
-        await (0, cache_store_1.optimisticallyInsert)(userId, collection, optimisticRecord);
-        // Add to write queue
-        await (0, cache_store_1.addToWriteQueue)(userId, {
-            id: generateId(),
-            type: 'insert',
-            collection,
-            data,
-        });
-        // Try network in background
-        this.request('POST', '/v1/sdk/db/insert', {
-            collection,
-            data,
-        })
-            .then(async (serverRecord) => {
-            // Invalidate cache so next query gets real data
+        try {
+            // Online path: await the server and return the authoritative record
+            // (with the server-assigned id). Refresh the collection cache so the
+            // next query sees real data instead of a stale optimistic copy.
+            const raw = await this.request('POST', '/v1/sdk/db/insert', { collection, data });
+            const record = (0, record_1.recordFromWire)(raw);
             await (0, cache_store_1.invalidateCache)(userId, collection);
-        })
-            .catch(() => {
-            // Will sync when online via SyncEngine
-        });
-        return optimisticRecord;
+            return record;
+        }
+        catch (e) {
+            // Server-reachable rejection: the server saw the request and refused.
+            // Surface to the caller without writing optimistic state or queuing —
+            // the server has already decided it will not accept this write, and
+            // queuing it would just spin SyncEngine until max retries.
+            if (e instanceof database_errors_1.KoolbaseDataError)
+                throw e;
+            // Genuine network failure → offline path: save to local cache and
+            // queue for SyncEngine to retry when online. Return the optimistic
+            // record so the UI has something to render in the meantime.
+            const optimisticRecord = {
+                id: generateId(),
+                createdBy: userId,
+                data,
+                createdAt: new Date().toISOString(),
+                updatedAt: new Date().toISOString(),
+            };
+            await (0, cache_store_1.optimisticallyInsert)(userId, collection, optimisticRecord);
+            await (0, cache_store_1.addToWriteQueue)(userId, {
+                id: generateId(),
+                type: 'insert',
+                collection,
+                data,
+            });
+            return optimisticRecord;
+        }
     }
     // ─── Upsert (online-only) ─────────────────────────────────────────────────
     /**
@@ -246,20 +263,39 @@ class KoolbaseDatabase {
         const raw = await this.request('GET', `/v1/sdk/db/records/${recordId}`);
         return (0, record_1.recordFromWire)(raw);
     }
-    // ─── Update ─────────────────────────────────────────────────────────────────
+    // ─── Update (online-first with offline fallback) ───────────────────────────
+    /**
+     * Update a record's fields by id.
+     *
+     * Online-first: awaits the server so a server-side rejection (unique
+     * violation, not found, permission denial) surfaces as the typed
+     * `KoolbaseDataError` subclass. An update that would violate a unique
+     * constraint now throws `KoolbaseConflictError` with the offending field —
+     * same shape as `insert` and `upsert`.
+     *
+     * On genuine network failure the update is queued for sync and a partial
+     * optimistic record is returned so the UI can re-render the new fields
+     * immediately.
+     */
     async update(recordId, data) {
         const userId = this.getUserId() ?? 'anonymous';
-        await (0, cache_store_1.addToWriteQueue)(userId, {
-            id: generateId(),
-            type: 'update',
-            recordId,
-            data,
-        });
         try {
             const raw = await this.request('PATCH', `/v1/sdk/db/records/${recordId}`, { data });
             return (0, record_1.recordFromWire)(raw);
         }
-        catch {
+        catch (e) {
+            // Server-reachable rejection: surface to caller without queuing — the
+            // server already refused the write and will refuse it again on retry.
+            if (e instanceof database_errors_1.KoolbaseDataError)
+                throw e;
+            // Genuine network failure → queue for sync and return an optimistic
+            // partial record so the UI reflects the update immediately.
+            await (0, cache_store_1.addToWriteQueue)(userId, {
+                id: generateId(),
+                type: 'update',
+                recordId,
+                data,
+            });
             return {
                 id: recordId,
                 data,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techfinityedge/koolbase-react-native",
-  "version": "3.1.0",
+  "version": "4.0.0",
   "description": "React Native SDK for Koolbase \u2014 auth, database, storage, realtime, feature flags, and functions in one package.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",