Okay, that might sound confusing. What I mean is that we want to normalize the frontend error handling by following JavaScript's Error conventions of having a name and a message property. At the moment, we usually (but not always) followed CouchDB's way having an error and a reason property.
As we change it throughout the code in the frontend, it will be needed to be changed in the backend as well, at least where objects are updated with an $error property, like in
Okay, that might sound confusing. What I mean is that we want to normalize the frontend error handling by following JavaScript's Error conventions of having a
nameand amessageproperty. At the moment, we usually (but not always) followed CouchDB's way having anerrorand areasonproperty.As we change it throughout the code in the frontend, it will be needed to be changed in the backend as well, at least where objects are updated with an
$errorproperty, like in