zitejs 0.9.96 → 0.9.98

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

@@ -26,6 +26,26 @@ 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 two of its own, both compiled to
+ * formulas in `integrations/airtable/formulas.ts`:
+ *
+ * - `equals` — explicit equality, alongside the bare-value shorthand.
+ * - `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.
+ */
+export type AirtableFilterCondition<V> = FilterCondition<V> & {
+    equals?: 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
@@ -43,12 +63,19 @@ export type RecordFilters<T> = {
 export type InferSchemaType<T> = T extends {
     _output: infer U;
 } ? U : T;
+/**
+ * SDK field names, with autocomplete, but not restricted to them: the runtime
+ * resolves a raw field id too ("Step 1: check if it's already a field ID" in
+ * `transformFieldsToFieldIds`). `string & {}` keeps the known keys as
+ * suggestions while still admitting an id, which `keyof T` alone would reject.
+ */
+export type FieldSelector<T> = Extract<keyof T, string> | (string & {});
 export interface TableFindAllOptions<T = Record<string, unknown>> {
     limit?: number;
     offset?: number;
     sort?: unknown[];
     filters?: RecordFilters<T>;
-    fields?: Array<Extract<keyof T, string>>;
+    fields?: Array<FieldSelector<T>>;
 }
 export interface BulkCreateResult<T> {
     success: boolean;
@@ -75,7 +102,7 @@ export interface TableClient<T, TInput = T> {
     findOne(params: {
         id?: string;
         filters?: RecordFilters<T>;
-        fields?: Array<Extract<keyof T, string>>;
+        fields?: Array<FieldSelector<T>>;
     }): Promise<T | undefined>;
     create(params: {
         record: Partial<TInput>;
@@ -118,6 +145,13 @@ export interface AuthUser {
 export type FindAllAuthUsersOptions = Omit<TableFindAllOptions<AuthUser>, "fields"> & {
     /** Restrict results to users belonging to any of these apps. */
     appIds?: string[];
+    /**
+     * Nested filter (`RecordsNestedFilterSchema`), the newer format alongside the
+     * flat `filters`. Only the auth client forwards it — the table `findAll` path
+     * destructures `{ filters, limit, offset, fields }` and drops it — which is
+     * why it lives here rather than on `TableFindAllOptions`.
+     */
+    filter?: unknown;
 };
 export type FindAllAuthUsersResult<T extends AuthUser = AuthUser> = {
     records: T[];
@@ -136,7 +170,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;
@@ -144,7 +178,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/runtime/index.d.ts

@@ -26,6 +26,26 @@ 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 two of its own, both compiled to
+ * formulas in `integrations/airtable/formulas.ts`:
+ *
+ * - `equals` — explicit equality, alongside the bare-value shorthand.
+ * - `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.
+ */
+export type AirtableFilterCondition<V> = FilterCondition<V> & {
+    equals?: 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
@@ -43,12 +63,19 @@ export type RecordFilters<T> = {
 export type InferSchemaType<T> = T extends {
     _output: infer U;
 } ? U : T;
+/**
+ * SDK field names, with autocomplete, but not restricted to them: the runtime
+ * resolves a raw field id too ("Step 1: check if it's already a field ID" in
+ * `transformFieldsToFieldIds`). `string & {}` keeps the known keys as
+ * suggestions while still admitting an id, which `keyof T` alone would reject.
+ */
+export type FieldSelector<T> = Extract<keyof T, string> | (string & {});
 export interface TableFindAllOptions<T = Record<string, unknown>> {
     limit?: number;
     offset?: number;
     sort?: unknown[];
     filters?: RecordFilters<T>;
-    fields?: Array<Extract<keyof T, string>>;
+    fields?: Array<FieldSelector<T>>;
 }
 export interface BulkCreateResult<T> {
     success: boolean;
@@ -75,7 +102,7 @@ export interface TableClient<T, TInput = T> {
     findOne(params: {
         id?: string;
         filters?: RecordFilters<T>;
-        fields?: Array<Extract<keyof T, string>>;
+        fields?: Array<FieldSelector<T>>;
     }): Promise<T | undefined>;
     create(params: {
         record: Partial<TInput>;
@@ -118,6 +145,13 @@ export interface AuthUser {
 export type FindAllAuthUsersOptions = Omit<TableFindAllOptions<AuthUser>, "fields"> & {
     /** Restrict results to users belonging to any of these apps. */
     appIds?: string[];
+    /**
+     * Nested filter (`RecordsNestedFilterSchema`), the newer format alongside the
+     * flat `filters`. Only the auth client forwards it — the table `findAll` path
+     * destructures `{ filters, limit, offset, fields }` and drops it — which is
+     * why it lives here rather than on `TableFindAllOptions`.
+     */
+    filter?: unknown;
 };
 export type FindAllAuthUsersResult<T extends AuthUser = AuthUser> = {
     records: T[];
@@ -136,7 +170,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;
@@ -144,7 +178,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/package.json

@@ -1,7 +1,7 @@
 {
   "name": "zitejs",
-  "version": "0.9.96",
-  "description": "The Zite framework \u2014 build apps on Zite Database",
+  "version": "0.9.98",
+  "description": "The Zite framework — build apps on Zite Database",
   "type": "module",
   "main": "./dist/cjs/index.js",
   "module": "./dist/esm/index.js",