cubic icon indicating copy to clipboard operation
cubic copied to clipboard

Handle errors during requests

Open Kaptard opened this issue 7 years ago • 1 comments

Right now, if an error occurs on either the API or Core node, it simply doesn't respond. Instead, we should put a try/catch around it on both the API and Core node, and return the error in plaintext in development, or encrypted in production.

Kaptard avatar Nov 06 '18 03:11 Kaptard

Updated a while ago to save the errors in the API's database (cubic-errors collection). Still requires sending the errors in the formats mentioned.

Kaptard avatar Jan 22 '20 08:01 Kaptard