Skip to main content

Model / Operation / Field Filtering

Model enable check: isModelEnabled — every model is enabled unless you explicitly disable it with models.<Model>.enabled: false. This holds in minimal mode too: minimal mode does not disable models, it only narrows the allowed operations (isOperationEnabled) and the set of object schemas that get emitted (isObjectSchemaEnabled).

Operation filtering: isOperationEnabled with alias mapping (createOne→create, etc.). Minimal mode reduces allowed ops unless overridden.

Schema-Level Filtering​

In minimal mode, entire schema types are filtered out to reduce complexity:

Blocked in minimal mode:

  • *CreateInput schemas (use *UncheckedCreateInput instead)
  • Nested relation inputs (*CreateNestedInput, *UpdateNestedInput)
  • Complex relation patterns (*CreateWithoutInput, *CreateOrConnectWithoutInput)
  • Aggregation inputs (*AggregateInput, etc.)
  • Select/Include helper schemas

Always allowed:

  • *UncheckedCreateInput (simple foreign key-based creation)
  • *UpdateInput and *UncheckedUpdateInput (update flexibility)
  • *UpdateManyMutationInput (updateMany payloads)
  • *WhereInput and *WhereUniqueInput (query filtering)
  • *OrderByWithRelationInput (sorting)

Helper schemas are allowed unconditionally, before the minimal-mode allow-list is consulted at all, because the schemas above reference them:

  • Scalar and enum filters plus their nullable forms (StringFilter, IntNullableFilter, EnumRoleFilter, EnumRoleNullableFilter)
  • Nested filters (NestedStringFilter, NestedIntNullableWithAggregatesFilter, …)
  • *WithAggregatesFilter variants
  • *FieldUpdateOperationsInput and Nullable*FieldUpdateOperationsInput

So minimal-mode output is larger than the "Always allowed" list alone suggests.

Field-Level Filtering​

Field filtering precedence (stop at first include win):

  1. model.fields.include
  2. Model variant excludeFields
  3. Legacy model.fields.exclude
  4. globalExclusions[variant]
  5. Global array legacy excludes

Wildcard patterns supported: field*, *field, *middle*.

WhereUniqueInput & strict base create inputs bypass variant exclusions to preserve shape fidelity.

Excluded relation fields cause foreign key scalar preservation for create inputs (maintain referential integrity constraints).

Optional Early Validation for WhereUniqueInput​

By default, WhereUniqueInput schemas include only unique selector fields (single-field uniques and named composite unique objects). Top-level keys are optional to match Prisma, and completeness for composite selectors is enforced by the nested composite object schemas themselves.

If you want early failure when no selector is present (e.g., rejecting {} before reaching Prisma), enable this opt-in flag in your JSON config:

zod-generator.config.json
{
  "validateWhereUniqueAtLeastOne": true
}

This adds a minimal superRefine that checks only the presence of at least one top-level selector. It does not enforce “exactly one” (Prisma will still validate that at runtime) and does not attempt to peek into nested composite fields (those are already required by their own schemas).