zitejs 0.9.97 → 0.9.99

package/dist/cjs/runtime/index.d.ts

@@ -15,9 +15,9 @@ export type FilterCondition<V> = {
     contains?: any;
     /** Not equal, or — against `null` — "is set". */
     not?: V | null;
-    /** Empty array means "no filter", not "match nothing". */
+    /** An empty array matches NOTHING — the SDK's filters convert to the nested format, where `in: []` is "is one of nothing". */
     in?: V extends Array<infer E> ? E[] : V[];
-    /** Empty array means "no filter", not "match everything". */
+    /** An empty array applies no filter at all — "is not one of nothing" is always true. */
     notIn?: V extends Array<infer E> ? E[] : V[];
     lt?: V | number | Date;
     lte?: V | number | Date;
@@ -26,6 +26,34 @@ export type FilterCondition<V> = {
 };
 /** Pre-monorepo name for {@link FilterCondition}. Kept so migrated app code that spells the type out still compiles. */
 export type FilterOperators<V> = FilterCondition<V> | V;
+/**
+ * Airtable's filter set is the shared one plus `ilike`, compiled to a formula in
+ * `integrations/airtable/formulas.ts`:
+ *
+ * - `ilike` — case-insensitive equality (`LOWER(f) = LOWER(v)`). Load-bearing:
+ *   the `zite.auth.ts` generated for a migrated user-sync app matches rostered
+ *   emails with it, because Airtable compares text case-sensitively while Zite
+ *   lowercases emails on some sign-in paths and not others.
+ *
+ * Kept separate from `FilterCondition` rather than merged into it, so a Zite DB
+ * filter can't offer an operator its runtime ignores.
+ *
+ * NOT `equals`, despite `formulas.ts` having a `case 'equals'`: that case only
+ * fires for the bare-value shorthand. `equals` is absent from
+ * `WhereConditionOperators`, so `isNestedCondition` doesn't recognize the
+ * object, the whole `{ equals: … }` is stringified as the operand, and Airtable
+ * 422s on `{Email}=[object Object]`.
+ *
+ * One operator per field on this path — `formulas.ts` reads
+ * `Object.keys(condition)[0]` and drops the rest, unlike the Zite DB filter
+ * builder which iterates them all.
+ */
+export type AirtableFilterCondition<V> = FilterCondition<V> & {
+    ilike?: V | V[];
+};
+export type AirtableRecordFilters<T> = {
+    [K in keyof T]?: T[K] | (T[K] extends Array<infer E> ? E : never) | AirtableFilterCondition<T[K]>;
+};
 /**
  * Filters keyed by the record's own field names. Typed rather than `unknown`
  * because an unrecognized key is not an error at runtime — it passes through
@@ -53,6 +81,13 @@ export type FieldSelector<T> = Extract<keyof T, string> | (string & {});
 export interface TableFindAllOptions<T = Record<string, unknown>> {
     limit?: number;
     offset?: number;
+    /**
+     * IGNORED on the table path. `DatabasesFindAllParamsSchema` has no `sort`
+     * key, so zod strips it before either dispatch, and neither destructures it.
+     * Kept in the type because removing it would only turn a silent no-op into a
+     * compile error for apps already passing it — the real fix is to forward it.
+     * It DOES work on `zite.auth.findAllUsers`, which is dispatched separately.
+     */
     sort?: unknown[];
     filters?: RecordFilters<T>;
     fields?: Array<FieldSelector<T>>;
@@ -150,7 +185,7 @@ export interface AirtableTableClient<T, TInput = T> {
         /** An opaque cursor from a previous call — not a row count. */
         offset?: string;
         limit?: number;
-        filters?: RecordFilters<T>;
+        filters?: AirtableRecordFilters<T>;
     }): Promise<{
         records: T[];
         offset: string | undefined;
@@ -158,7 +193,7 @@ export interface AirtableTableClient<T, TInput = T> {
     }>;
     findOne(params: {
         id?: string;
-        filters?: RecordFilters<T>;
+        filters?: AirtableRecordFilters<T>;
     }): Promise<T | undefined>;
     create(params: {
         record: Partial<TInput>;

package/dist/cjs/sync/lib.js

@@ -411,8 +411,8 @@ function generateDbTs(schema) {
     lines.push("//   .findAll({ filters?, sort?, offset?, limit?, fields? }) → { records: T[], hasMore: boolean }");
     lines.push("//     filters: { fieldName: value } for equality, or { fieldName: { <op>: value } }");
     lines.push("//     operators: contains, not, in, notIn, lt, lte, gt, gte");
-    lines.push('//       `not: null` means "is set"; `in`/`notIn` with an empty array apply NO filter');
-    lines.push("//     sort: [{ field: 'fieldName', direction: 'asc' | 'desc' }]");
+    lines.push('//       `not: null` means "is set". An empty `in: []` matches nothing; an', '//       empty `notIn: []` applies no filter.');
+    lines.push("//     sort is currently IGNORED here — it is stripped before the request.", "//       (it does work on zite.auth.findAllUsers). Order in SQL instead.");
     lines.push("//     limit defaults to 500, max 2000; offset is a row count (a number)");
     lines.push("//   .findOne({ id?, filters?, fields? }) → T | undefined");
     lines.push("//   .create({ record }) → T");

package/dist/esm/runtime/index.d.ts

@@ -15,9 +15,9 @@ export type FilterCondition<V> = {
     contains?: any;
     /** Not equal, or — against `null` — "is set". */
     not?: V | null;
-    /** Empty array means "no filter", not "match nothing". */
+    /** An empty array matches NOTHING — the SDK's filters convert to the nested format, where `in: []` is "is one of nothing". */
     in?: V extends Array<infer E> ? E[] : V[];
-    /** Empty array means "no filter", not "match everything". */
+    /** An empty array applies no filter at all — "is not one of nothing" is always true. */
     notIn?: V extends Array<infer E> ? E[] : V[];
     lt?: V | number | Date;
     lte?: V | number | Date;
@@ -26,6 +26,34 @@ export type FilterCondition<V> = {
 };
 /** Pre-monorepo name for {@link FilterCondition}. Kept so migrated app code that spells the type out still compiles. */
 export type FilterOperators<V> = FilterCondition<V> | V;
+/**
+ * Airtable's filter set is the shared one plus `ilike`, compiled to a formula in
+ * `integrations/airtable/formulas.ts`:
+ *
+ * - `ilike` — case-insensitive equality (`LOWER(f) = LOWER(v)`). Load-bearing:
+ *   the `zite.auth.ts` generated for a migrated user-sync app matches rostered
+ *   emails with it, because Airtable compares text case-sensitively while Zite
+ *   lowercases emails on some sign-in paths and not others.
+ *
+ * Kept separate from `FilterCondition` rather than merged into it, so a Zite DB
+ * filter can't offer an operator its runtime ignores.
+ *
+ * NOT `equals`, despite `formulas.ts` having a `case 'equals'`: that case only
+ * fires for the bare-value shorthand. `equals` is absent from
+ * `WhereConditionOperators`, so `isNestedCondition` doesn't recognize the
+ * object, the whole `{ equals: … }` is stringified as the operand, and Airtable
+ * 422s on `{Email}=[object Object]`.
+ *
+ * One operator per field on this path — `formulas.ts` reads
+ * `Object.keys(condition)[0]` and drops the rest, unlike the Zite DB filter
+ * builder which iterates them all.
+ */
+export type AirtableFilterCondition<V> = FilterCondition<V> & {
+    ilike?: V | V[];
+};
+export type AirtableRecordFilters<T> = {
+    [K in keyof T]?: T[K] | (T[K] extends Array<infer E> ? E : never) | AirtableFilterCondition<T[K]>;
+};
 /**
  * Filters keyed by the record's own field names. Typed rather than `unknown`
  * because an unrecognized key is not an error at runtime — it passes through
@@ -53,6 +81,13 @@ export type FieldSelector<T> = Extract<keyof T, string> | (string & {});
 export interface TableFindAllOptions<T = Record<string, unknown>> {
     limit?: number;
     offset?: number;
+    /**
+     * IGNORED on the table path. `DatabasesFindAllParamsSchema` has no `sort`
+     * key, so zod strips it before either dispatch, and neither destructures it.
+     * Kept in the type because removing it would only turn a silent no-op into a
+     * compile error for apps already passing it — the real fix is to forward it.
+     * It DOES work on `zite.auth.findAllUsers`, which is dispatched separately.
+     */
     sort?: unknown[];
     filters?: RecordFilters<T>;
     fields?: Array<FieldSelector<T>>;
@@ -150,7 +185,7 @@ export interface AirtableTableClient<T, TInput = T> {
         /** An opaque cursor from a previous call — not a row count. */
         offset?: string;
         limit?: number;
-        filters?: RecordFilters<T>;
+        filters?: AirtableRecordFilters<T>;
     }): Promise<{
         records: T[];
         offset: string | undefined;
@@ -158,7 +193,7 @@ export interface AirtableTableClient<T, TInput = T> {
     }>;
     findOne(params: {
         id?: string;
-        filters?: RecordFilters<T>;
+        filters?: AirtableRecordFilters<T>;
     }): Promise<T | undefined>;
     create(params: {
         record: Partial<TInput>;

package/dist/esm/sync/lib.js

@@ -401,8 +401,8 @@ export function generateDbTs(schema) {
     lines.push("//   .findAll({ filters?, sort?, offset?, limit?, fields? }) → { records: T[], hasMore: boolean }");
     lines.push("//     filters: { fieldName: value } for equality, or { fieldName: { <op>: value } }");
     lines.push("//     operators: contains, not, in, notIn, lt, lte, gt, gte");
-    lines.push('//       `not: null` means "is set"; `in`/`notIn` with an empty array apply NO filter');
-    lines.push("//     sort: [{ field: 'fieldName', direction: 'asc' | 'desc' }]");
+    lines.push('//       `not: null` means "is set". An empty `in: []` matches nothing; an', '//       empty `notIn: []` applies no filter.');
+    lines.push("//     sort is currently IGNORED here — it is stripped before the request.", "//       (it does work on zite.auth.findAllUsers). Order in SQL instead.");
     lines.push("//     limit defaults to 500, max 2000; offset is a row count (a number)");
     lines.push("//   .findOne({ id?, filters?, fields? }) → T | undefined");
     lines.push("//   .create({ record }) → T");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zitejs",
-  "version": "0.9.97",
+  "version": "0.9.99",
   "description": "The Zite framework — build apps on Zite Database",
   "type": "module",
   "main": "./dist/cjs/index.js",