Timeline for Best practice in synchronized form data validations (Web apps - Client-Server)
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 27, 2020 at 8:40 | comment | added | Brian Burton | You may be overlooking the value of this strategy. This is just the top layer of validation, the boring sanity checks that need to be performed on the front and back end. If “name” has a max 64 chars in the front, the back needs the same rule. If the frontend uses Angular Validators and the backend uses Joi, you have two completely different implementations for the same rules. This strategy homogenizes that first basic level of validation that you can then add more stringent validations to avoid security issues where a field might be erroneously required on the front but not on the back | |
| Nov 27, 2020 at 8:11 | comment | added | Rik D | @Nachiappan-Kumarappan mentioned some drawbacks of an approach like this in his answer. I would further argue that this only applies to the very simplest form of validation, stuff that hardly even matters. Important business rules are often more complex and it will be hard to capture in a scheme like this. For example 'email is required for users from country x' or 'amount of ordered items can only be changed until the next business day 6pm'. | |
| Nov 26, 2020 at 13:35 | review | First posts | |||
| Nov 27, 2020 at 7:58 | |||||
| Nov 26, 2020 at 13:33 | history | answered | Brian Burton | CC BY-SA 4.0 |