Zod and form-level errors about sveltekit-superforms HOT 3 CLOSED

So I think the Zod approach could work - adding an _errors property to the object. That's what's done with array errors already, so it's not much extra work.

Yes, that would be a good approach. It might also be a good idea to enable manually adding to $errors._errors by calling setError without specifying a field (e.g., setError(form, null, 'There was a form-level problem')).

Using form.message is perhaps more for a flash message than actual validation errors, but if you want to use it, have you seen the new message helper method: https://github.com/ciscoheat/sveltekit-superforms/discussions/76

Didn't know about that. Thanks.

from sveltekit-superforms.

@abastardi In the upcoming 0.6.7 version, this will be added. Thank you for a good suggestion!

from sveltekit-superforms.

I've been thinking about updating that for a long time! But I'm working on the documentation site, so it will soon be fixed.

$errors is not a Record<string, string[]>, but a nested object that mirrors $form, but every "leaf" of the object is a string[] instead of the form value (with some crazy types that handles the inference). For example:

{
  user: {
    posts: {
      "0": { 
        title: ['The title is too short'] 
      }
    }
  }
}

I haven't considered that errors may be added to the form itself like you do, and errors should not be an array instead of an object. So I think the Zod approach could work - adding an _errors property to the object. That's what's done with array errors already, so it's not much extra work.

Using form.message is perhaps more for a flash message than actual validation errors, but if you want to use it, have you seen the new message helper method: https://github.com/ciscoheat/sveltekit-superforms/discussions/76

from sveltekit-superforms.