How should I provide detailed information about an error, if not through HTTP status codes?
This question comes from here. I believe it deserves to be on its own instead of being lost in a long question with multiple points.
How should I provide detailed information about an error, if not through HTTP status codes?
This question comes from here. I believe it deserves to be on its own instead of being lost in a long question with multiple points.
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]
Why is there “Unknown error” in real life? [duplicate]
This question already has answers here: How much information about an error should be shown to the user? (6 answers) Closed 9 years ago. As a programmer, I always try my best to explain what happened in the code when I have to show an error message, for example: try { int a = b […]