3 ms·
It's hard to give a generic answer to this. I just see way too many bad error messages that could be solved with a little more thought and copywriting skills.
by tiborsaas 4y ago
It's hard to give a generic answer to this. I just see way too many bad error messages that could be solved with a little more thought and copywriting skills.
Error messages are part of the user experience and they should not be an afterthought.
If errors are nested, list them all. Give a generic feedback then, and also provide a technical explanation that would help debugging. Most importantly, we should make the user feel safe and in control as much as possible.
- llanowarelves 4y agoI actually do like "collecting" the errors when possible, and having them return in the API response (for example). Instead of the common pattern where there's just singular "error:" in the top-level json. Works great for things like validation.