How to Support Warning and Error Handling, and Ensure Warnings Do Not Block Form Submission?

[vismayZN]

We are looking for guidance on how to effectively handle warnings and errors in the form submission process, specifically:

• Distinguishing Between Warnings and Errors: How can we implement a form that clearly differentiates between warnings (which alert users but allow form submission) and errors (which require action and should block submission)?

[nickgros]

If you disable HTML5 validation, the form data can still be submitted with errors and your onSubmit logic can still be used to pass data.

To disambiguate 'warnings' and 'errors' might be more complicated. Some users have modified the error object to indicate if it's a warning but you have to add your own custom validation code to do so. Then you need to update the UI components to treat these differently, and handle errors/warnings separately in your event handlers. It should all be possible with all of the customization options that RJSF provides, but it's not something that RJSF supports as a first-class feature.

[vismayZN]

Appreciate your help, @nickgros.

I wanted to check if there's a way to implement functionality similar to JSON Schema — where the form can be rendered and validated based on a defined schema. However, in my case, I also need to support warnings, which require a separate logic to validate individual fields.

It would be really helpful if there's a way to define a schema for warnings as well, ideally keeping the form re-renders to a minimum. Otherwise, forms with a large number of fields tend to feel sluggish due to excessive re-rendering.

Let me know your thoughts. Thanks again!