@rebasepro/client 0.14.1-canary.g7e666eb → 0.14.1

package/dist/index.es.js

@@ -4104,6 +4104,13 @@ function matchesParams(row, params) {
 * Sort in place, Postgres-style: nulls last ascending, first descending, with
 * the row id as a tiebreak so paging through an unsorted-but-equal run does
 * not shuffle rows between pages.
+*
+* The tiebreak runs *descending*, which is not a taste: every server-side sort
+* ends on `id DESC` — `FetchService.buildOrderExpressions` appends it to make
+* the ordering total, and the keyset cursor is built to match. This ran
+* ascending, so two rows sharing a sort value came back from the local overlay
+* in the opposite order to the server's, and {@link isLocallySortable} called
+* that page exactly reproducible while it was not.
 */
 function sortRows(rows, orderBy) {
 	const keys = normalizeOrderBy(orderBy);
@@ -4130,8 +4137,10 @@ function compareOnKey(a, b, field, direction) {
 	if (cmp === void 0 || cmp === 0) return 0;
 	return cmp * (direction === "desc" ? -1 : 1);
 }
+/** The last word, and the server's: `id DESC`. */
 function tiebreak(a, b) {
-	return compareValues(a.id, b.id) ?? 0;
+	const cmp = compareValues(a.id, b.id);
+	return cmp === void 0 ? 0 : -cmp;
 }
 /**
 * Resolve `page`/`offset`/`limit` the way the server does.