Schema Validation Just Stopped Working

[chiester]

Any idea why schema validation would just stop working?

Async validation via onValidate works. But violations of the schema do not trigger <ErrorField> to render.

[chiester]

Also, it's still not clear to me how to get error or validation messages back to ErrorField from either sync or async validation to present in the UI.

[chiester]

If I remove onValidate, the schema validation works. When I put it back in, schema vaildation does not work at all, even if all the onValidate function does is return null.

[radekmie]

Hi @chiester. I think the onValidate part got answered in #1257, and this part is clear (if not, let's continue there).

When it comes to ErrorField, it displays the errors using the bridge's getError, i.e., it extracts the field error out of the form error. To make your custom error renders in there, you'd need to make sure the error matches the format of your bridge's errors. For example, the JSON Schema bridge works using the details field.

(Side note: if possible, please edit the first message rather than adding multiple ones, as it's easier to follow the threads then.)