Validator tests · Genus Examples

Basics — required, lengths, formats

Name (required, min-length 3)

Email (required, email)

Age (optional: integer 18–99)

Website (optional: url)

Code (pattern + custom message)

Bio (optional: max-length 100)

Cross-field + custom rule — same-as, a rule registered at init

Password (required, password policy)

Confirm password (same-as)

Lucky number (custom rule: divisible-by 5)

Components — the same attributes on selekt / date-selekt / file-selekt

Country (selekt, required)

Colors (selekt multiple, 2–3 items)

Start date (date-selekt, required)

Document (file-selekt, required)

Interests (checkbox group, min-items 2 — rules on the first box)

Code

Music

Sport

Plan (radio group, required)

Free

Pro

I accept the terms

Notifications (switch, required)

Marketing emails (reverse: label first)

Server validation — /examples-demo/validate/username via g.fetch, team attached

Team (sent along via validate-server-attach)

Username (required + server, on change)

Username (live: validate-on="keyup")

Taken everywhere: admin, root, genus. Taken only in team Alpha: john. "boom" = business-error demo. The endpoint answers with ~250ms latency; the live field validates as you type (debounced, stale requests aborted).

Result

Submit with errors → toast + messages under the fields. Submit clean → validator:submit fires and the FormData lands here (this is where the app would call g.fetch).

(nothing submitted yet)