logaritmisk/biggus-dickus
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases Wiki Activity

Per-field validation rules (min/max, length, regex) for field definitions #11

New Issue
Open
opened 2026-06-02 08:47:08 +00:00 by logaritmisk · 0 comments
logaritmisk commented 2026-06-02 08:47:08 +00:00
Owner
Copy Link
Copy Source

Spec §6.2 lists "validation rules" as part of a field definition. The MVP registry (crates/db/migrations/0004_field_definition.sql, domain::FieldDefinition) ships type + required + vocabulary/authority binding only — no general per-field rules (numeric min/max, string length, regex/pattern, allowed-range for dates, etc.).

Plan 5 (object JSONB values + validation) will validate values against type + required + binding as-is. If/when richer rules are wanted, add them as an additive migration (a rules column or a field_definition_rule table) plus a validation step — FieldType-orthogonal, so it layers on without disturbing the registry's shape.

Source: Plan 4 (field-definition registry) final review — deliberate MVP scope cut, recorded for later.

Spec §6.2 lists "validation rules" as part of a field definition. The MVP registry (`crates/db/migrations/0004_field_definition.sql`, `domain::FieldDefinition`) ships **type + `required` + vocabulary/authority binding** only — no general per-field rules (numeric min/max, string length, regex/pattern, allowed-range for dates, etc.). Plan 5 (object JSONB values + validation) will validate values against **type + required + binding** as-is. If/when richer rules are wanted, add them as an additive migration (a rules column or a `field_definition_rule` table) plus a validation step — `FieldType`-orthogonal, so it layers on without disturbing the registry's shape. _Source: Plan 4 (field-definition registry) final review — deliberate MVP scope cut, recorded for later._
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
logaritmisk
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: logaritmisk/biggus-dickus#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?