FA-8564 / Form validation / Member archive

Constraint validation priority: Unparseable user input is reported valid · case 04

Unparseable user input is reported valid.

Member previewVariant 4 · 3 implementations · 13 checks per implementation

Case contract

Required checks distinguish blank from zero; malformed input precedes numeric checks; optional blank is valid; min/max are inclusive; pattern applies last.

Why this case matters

A deterministic model of constraint validation priority; this isolates one interface invariant without requiring a browser.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
bad	`null`	`"bad-input"`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.