Production diagnostics
Error codes
Attaform keeps production diagnostics compact: each condition throws or logs as a stable code in the shape [attaform] AF10 attaform.dev/e/af10, and the link in the message lands here. Development builds carry the full explanation inline instead, so the fastest way to a rich message is running the same interaction on a dev build.
Codes are stable identifiers. A retired code is never reassigned, and the message text around a code can evolve without notice; branch on the error class or the code, never on the prose. Each page describes the current release, v0.31.3: the code's meaning holds across versions, while the quoted development message and the fix guidance track the latest code.
15 codes
- AF01The schema and the adapter disagree on the Zod major version
- AF02Retired: a schema kind Attaform refused at construction
- AF03Retired: the adapter met a Zod kind it did not recognize
- AF04
useFormreceived an invalid configuration - AF05A form key uses the reserved
__atta:namespace - AF06
useForm/injectFormran outside Vuesetup() - AF07No Attaform registry is attached to the Vue app
- AF08A numeric path segment is not a non-negative integer
- AF09A dotted path contains an empty segment
- AF10
form.rehydrate()ran without adefaultValuesfactory - AF11
resetFieldcould not restore a leaf from originals - AF12
resetFieldcould not restore a subtree from originals - AF13The Zod v3 adapter hit its blank-derivation backstop
- AF14A
registertransform threw and the write was aborted - AF15The
useFormschema root cannot hold keys