primitive-admin 1.0.54 → 1.0.56

package/dist/src/lib/db-codegen/dbGenerator.d.ts

@@ -6,28 +6,19 @@
  * then either (a) writes them, or (b) compares them against on-disk for
  * `--check`. No commander dependency, no `process.exit`.
  *
- * Reuses the codegen-v2 machinery:
- *   - `loadSchemaFromTomlString` (the shared `[models.*]` parser) for record
- *     interfaces — the database-type `[models.*]` blocks round-trip through
- *     the same loader and the same `FieldType` vocabulary.
- *   - The banner + fingerprint header pattern and stale-output cleanup.
- *
- * Adds the OPERATIONS half (op-params interfaces + per-op result aliases)
- * that codegen-v2 has no analog for. A result alias is derived from `op.type`
- * and, where the shape is derivable, the op's parsed `definition`: a query op's
- * `projection` (#1439), a mutation op's step kinds (#1438), and a pipeline op's
- * `return` step (#1437). This file resolves those into the small descriptors
- * the templates consume; the templates stay pure string-emitters.
+ * The op/record RESOLUTION (parse, schema load, required-ness inference, op
+ * params, and per-op result descriptors) lives in the shared, naming-neutral
+ * `describeDbType` IR (`dbTypeIR.ts`) — the SAME source the Swift renderer
+ * (`swift-codegen/dbGenerator.ts`) consumes (issue #1547 binding 5). This file
+ * is now purely the TS *rendering* half: it applies TS identifier naming
+ * (`resolveRecordInterfaceName`, `opParamsInterfaceName`, …) to that IR and
+ * emits `*.generated.ts` via the pure `dbTemplates` string-emitters. The
+ * emitted bytes are unchanged from the former inline implementation.
  */
 import { type GeneratedFileMismatch } from "../codegen-shared/generatedFiles.js";
-export interface DbCodegenInput {
-    /** Database type name (drives the output filename). */
-    databaseType: string;
-    /** Path to the source `database-types/<type>.toml` file. */
-    tomlPath: string;
-    /** Raw TOML content (already read from disk). */
-    tomlContent: string;
-}
+import { type DbCodegenInput } from "./dbTypeIR.js";
+export type { DbCodegenInput } from "./dbTypeIR.js";
+export { inferArrayParamElementTypes, inferRequiredRecordFields, type InferredRecordModelInfo, } from "./dbTypeIR.js";
 export interface GenerateDbTypesOptions {
     /** One entry per database-type TOML file to generate from. */
     inputs: DbCodegenInput[];
@@ -68,69 +59,6 @@ export type DbCheckMismatch = GeneratedFileMismatch;
  * TOML. Exported so tests can assert on the rendered string directly.
  */
 export declare function renderDbTypeFile(input: DbCodegenInput): string;
-/**
- * Infer the scalar element TS type for op params consumed by a `$in`/`$nin`
- * filter operator (#1488, Phase 1). Codegen-only: a param compared with
- * `$in`/`$nin` against a model field is definitionally an array, so the
- * typed-ops factory (#1441) should emit `<elem>[]` rather than widening an
- * untyped/object param to `Record<string, unknown>` (which `string[]` is not
- * assignable to).
- *
- * Kept a small local helper next to {@link inferRequiredRecordFields} rather
- * than a shared cross-runtime analysis pass (sponsor decision on #1488).
- *
- * Returns a map of param name → element TS type. The `"unknown"` sentinel means
- * "emit `unknown[]`" — used when the compared field is missing from the model
- * schema (or the op has no resolvable model), when the same param is bound to
- * fields of differing element types, or when the param is also used as a scalar
- * elsewhere (conservative widen, mirroring #845's disagreement rule / #1488
- * Fork 4). A param absent from the map is not consumed by any array operator
- * and keeps its declared-type mapping (inference never widens such a param).
- */
-export declare function inferArrayParamElementTypes(op: any, fieldTypesByModel: Map<string, Map<string, string>>): Map<string, string>;
-/**
- * Per-model result of {@link inferRequiredRecordFields}. Shaped as an object
- * (rather than a bare `Set`) so it can grow additional inferred metadata later
- * without changing the call-site contract — e.g. future alignment with #845's
- * server-side op-params analysis. For now it carries only the set of record
- * fields the operation params prove are always supplied at create time.
- */
-export interface InferredRecordModelInfo {
-    /** Record field names promoted to non-optional by op-params inference. */
-    fields: Set<string>;
-}
-/**
- * Infer which record fields are always supplied at create time, by reading the
- * `save` operation params (issue #842).
- *
- * A field is promoted to required for a model only if:
- *   - at least one `save` (create) op writes it from a bare `$params.X`
- *     binding, AND
- *   - EVERY `save` op that writes the field binds it to a param declared
- *     `required: true` (the "ALL writers agree" rule).
- *
- * Deliberately conservative:
- *   - `patch` (and every non-`save` inner op) is excluded — partial updates
- *     don't guarantee creation-time presence.
- *   - whole-object saves (`data = "$params.X"`, a string rather than a
- *     per-field map) carry no field-level mapping, so no field can be promoted
- *     from them (Q4 skip).
- *   - only an EXACT top-level bare `$params.X` value counts (the whole binding
- *     value must match `^\$params\.X$`, and `X` must be a declared top-level
- *     param). A literal, computed, partially-interpolated value, or a nested
- *     path (`$params.obj.sub`) never promotes a field — a nested sub-property
- *     may be absent even when the top-level object param is required. This is
- *     deliberately stricter than the CLI's lenient `collectParamRefs`
- *     first-segment rule, which is fine for its validation use but would
- *     wrongly promote nested bindings here.
- *   - inner ops are matched to the record model by the inner op's own
- *     `modelName` when present, falling back to the enclosing operation's
- *     `modelName`.
- *
- * Pure: no I/O, no mutation of the input. The caller OR's the result with the
- * schema-level `required` flag, so inference only ever ADDS requiredness.
- */
-export declare function inferRequiredRecordFields(operations: any[]): Map<string, InferredRecordModelInfo>;
 /**
  * Run codegen end-to-end across one or more database-type TOML inputs. The
  * disk lifecycle (write / `--check` / stale cleanup) is delegated to the