if there is a specific case that is not possible with the current implementation, please let us know

I have 2 cases where I had a hard time implementing a feature. We were migrating from Formik which does have a Context that we can use to get the detail we needed;

1) handling server-side errors. Then we get a response back from the server that contains possible validation errors,  would like to do a pass over the keys in the error object to see if they line up with names of form fields. If so, I return these errors from the Form's `validator` so that they are shown inline in the form. For other errors that did not match a form field, I show them in a toast/alert popup. This would be a lot easier to do with the Form's `fields`property, which it holds internally.

2) Displaying all validation errors in a single panel element. This one is an unfortunate side-effect of some big forms that we have, that are split into multiple tab views. Unfortunately I can't change the API right now and it requires the entire multi-view form to be submitted at once. This can result in server-side validation errors for form elements that are in different hidden tabs or collapsed panels. As a workaround, we were just going to put all the errors in a single element that is always visible at the top of the page. This isn't terrible hard to do for showing errors that come back from the server, but for form fields that have their own `validator` function, those always return errors even when a field is untouched, so for things like required fields, validation errors would show up immediately. The Kendo Field component works around this by passes the prop

valid: !(Boolean(form.errors[name]) && form.touched[name]),

But from outside the element, all we get is a single "touched" boolean for the entire form, not which individual fields have been touched. That data is in the context.