You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you post the form to the server ( or where ever) you have to do some server side validation for cross cutting edge cases & concerns.
validate that any data referenced ( like an enum, KV value ) is still in the DB.
any business logic checks.
SO what is probably also needed is a standard approach for showing Server side errors relating to a form.
If the error is unrelated to a specific form field ( like a business logic error), then show it at the bottom where the submit button is since that is where the user is visually in the scroll.
This should be baked into the Submit Button Widget maybe. Up for debate..
If the error relates to one or more fields, then show the server side error against those fields.
once the user has change those fields, the error goes away, allowing the user to try again.
I noticed you have support already for server side errors coming back, but no formal support for how to handle it.
So if we can bake this into the example if would be worthwhile.
Please ask if you have any questions as i have had to deal with this stuff quite a bit on many projects.
The text was updated successfully, but these errors were encountered:
I just tried the example and noticed something..
When you post the form to the server ( or where ever) you have to do some server side validation for cross cutting edge cases & concerns.
SO what is probably also needed is a standard approach for showing Server side errors relating to a form.
I noticed you have support already for server side errors coming back, but no formal support for how to handle it.
So if we can bake this into the example if would be worthwhile.
Please ask if you have any questions as i have had to deal with this stuff quite a bit on many projects.
The text was updated successfully, but these errors were encountered: