future: Propagate meaningful errors to frontend without exposing sensitive info #137
Description
Moto
The users need to know what exactly went wrong with their form submission if an error is thrown. Currently we are sending only Request is malformed or Oops! Something went wrong messages and it is clearly not helping users as well as developers.
Suggested changes
- Change Request malformed messages to proper messages like
"Student 1 not registered for anokha","Invalid request body" - Lets throw 500 error and messages only for issues that are caused in backend.