runeforge 0.0.60 → 0.0.61

package/README.md

@@ -945,7 +945,8 @@ config={{
 
 A few things worth knowing about how reorder mode behaves:
 
-- **The list is ordered by `attribute` ascending (or `compare`, see below) the whole time reorder is active** — not by `_id`, not by whatever order the backend/array happens to return, and not by clicking a column header either: column-header sorting is unavailable while `config.reorder` is set, since row order needs a single, unambiguous source of truth for dragging to mean anything. This holds even if `attribute` is `excludedFromList` and has no column of its own — ordering reads the raw row value regardless of what's rendered. Per-column filters are unavailable for the same reason (a filtered-out row's position would become undefined).
+- **The list is ordered by `attribute` ascending (or `compare`, see below) the whole time reorder is active** — not by `_id`, not by whatever order the backend/array happens to return, and not by clicking a column header either: column-header sorting is unavailable while reorder is active, since row order needs a single, unambiguous source of truth for dragging to mean anything. This holds even if `attribute` is `excludedFromList` and has no column of its own — ordering reads the raw row value regardless of what's rendered.
+- **Column filters and reorder share the table, but not at the same time.** Filter controls stay visible the whole time — as soon as any column filter is set, reorder pauses (drag handles disappear, column-header sorting comes back, and the table behaves like a plain filtered/sorted one) since a filtered-out row's drag position would be undefined. Clearing every active filter resumes reorder automatically, back to `attribute`/`compare` ordering.
 - **Pagination stays on.** To move a row across a page boundary, drag it to the narrow zone at either edge of the table and hold — after `pageFlipThresholdMs` (default `2000`) it flips to the previous/next page; keep hovering (without letting go) to flip again. Drop once you're on the right page.
 - It's **not supported in [server-pagination mode](#server-side-pagination-sorting--filtering)** (a `PaginatedEnvelope` `data`) — cross-page drag positions aren't meaningful without a lot more server-side machinery, so `config.reorder` is ignored whenever server pagination is active.
 - Set `enabled: false` to keep the configuration in place (attribute, endpoint, icon) but temporarily turn dragging off, without having to remove the whole object.

package/dist/components/table/PaginatedTable.svelte

@@ -59,11 +59,13 @@
 		/** Current ordering + filters snapshot, kept in sync for callers that
 		 * need to replicate the active query (e.g. exporting server-side). */
 		query?: TableQuery;
-		/** Turns on drag-to-reorder. Per-column filters are suppressed and row
-		 * order is fully owned by `reorder.compare`/`reorder.attribute` while
-		 * it's active — ignored entirely in server-pagination mode
-		 * (`pagination` set), since the full row set needs to be reachable
-		 * client-side for drag positions to be meaningful. */
+		/** Turns on drag-to-reorder. Row order is fully owned by
+		 * `reorder.compare`/`reorder.attribute` while it's active — active only
+		 * when no column filter is currently set (a filter pauses reorder
+		 * until it's cleared, see `reorderActive` below) and never in
+		 * server-pagination mode (`pagination` set), since the full row set
+		 * needs to be reachable client-side for drag positions to be
+		 * meaningful. */
 		reorder?: ReorderOptions<T>;
 		/** Fires after a drag settles with the complete reordered row list
 		 * (client mode only). The caller decides how to persist it. */
@@ -94,8 +96,12 @@
 
 	// Server-pagination mode owns its own full row set server-side, where
 	// drag positions can't be reconciled across pages — reorder only makes
-	// sense once the whole (client-mode) row set is reachable.
-	const reorderActive = $derived(!!reorder && !pagination);
+	// sense once the whole (client-mode) row set is reachable. An active
+	// column filter pauses reorder the same way: a filtered-out row's drag
+	// position would be undefined, so reorder mode steps aside (and the
+	// table behaves like a plain sortable/filterable one) for as long as any
+	// filter stays on, resuming automatically once every filter clears.
+	const reorderActive = $derived(!!reorder && !pagination && !filter.hasAny());
 
 	const indexed = $derived(data.map((row, index): IndexedRow<T> => ({ row, index })));
 	// Dragging needs the complete row set reachable, so filters (which would

package/dist/components/table/PaginatedTable.svelte.d.ts

@@ -27,11 +27,13 @@ declare function $$render<T extends object = Record<string, unknown>>(): {
         /** Current ordering + filters snapshot, kept in sync for callers that
          * need to replicate the active query (e.g. exporting server-side). */
         query?: TableQuery;
-        /** Turns on drag-to-reorder. Per-column filters are suppressed and row
-         * order is fully owned by `reorder.compare`/`reorder.attribute` while
-         * it's active — ignored entirely in server-pagination mode
-         * (`pagination` set), since the full row set needs to be reachable
-         * client-side for drag positions to be meaningful. */
+        /** Turns on drag-to-reorder. Row order is fully owned by
+         * `reorder.compare`/`reorder.attribute` while it's active — active only
+         * when no column filter is currently set (a filter pauses reorder
+         * until it's cleared, see `reorderActive` below) and never in
+         * server-pagination mode (`pagination` set), since the full row set
+         * needs to be reachable client-side for drag positions to be
+         * meaningful. */
         reorder?: ReorderOptions<T>;
         /** Fires after a drag settles with the complete reordered row list
          * (client mode only). The caller decides how to persist it. */

package/dist/components/table/TableHeader.svelte

@@ -70,7 +70,7 @@
             direction={reorderActive ? null : sort.directionFor(col.attribute)}
             onsort={() => sortBy(col)}
           />
-          {#if isFilterable(col) && !reorderActive}
+          {#if isFilterable(col)}
             <ColumnFilter
               column={col}
               entries={distinctValues[col.attribute] ?? []}

package/dist/components/table/state.svelte.d.ts

@@ -26,6 +26,7 @@ export declare class FilterState {
         to: string;
     };
     hasActive(attribute: string): boolean;
+    hasAny(): boolean;
     isChecked(attribute: string, value: string): boolean;
     setText(attribute: string, value: string): void;
     toggleValue(attribute: string, value: string): void;

package/dist/components/table/state.svelte.js

@@ -66,6 +66,18 @@ export class FilterState {
             (this.values.get(attribute)?.size ?? 0) > 0 ||
             !!(this.dateRanges.get(attribute)?.from || this.dateRanges.get(attribute)?.to));
     }
+    hasAny() {
+        for (const value of this.text.values())
+            if (value)
+                return true;
+        for (const set of this.values.values())
+            if (set.size > 0)
+                return true;
+        for (const range of this.dateRanges.values())
+            if (range.from || range.to)
+                return true;
+        return false;
+    }
     isChecked(attribute, value) {
         return this.values.get(attribute)?.has(value) ?? false;
     }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "runeforge",
-  "version": "0.0.60",
+  "version": "0.0.61",
   "description": "SvelteKit toolkit for building metadata-driven CRUD interfaces with tables, forms, and actions",
   "license": "MIT",
   "author": "Ezequiel Puerta",