Handling and Reporting Non-Defect Errors in a Full Stack RPC Service
I'm creating a full stack RPC service. It's not customer facing so I'm okay with detailed error messages showing up on the client.
Is there an idiomatic way to both recover from non-defect errors while still reporting that the error happened somewhere?
It's so that my app is still functional even with bugs, but I can get info in the HTTP payload about the bug to fix it at a later time.
Is there an idiomatic way to both recover from non-defect errors while still reporting that the error happened somewhere?
It's so that my app is still functional even with bugs, but I can get info in the HTTP payload about the bug to fix it at a later time.
