Currently, some of our endpoints use "old" error objects, while others use "new" error objects. This inconsistency creates challenges in reducing technical debt. We need to adopt the "new" approach for all endpoints.
DoD
There is no regression in error handling across the entire application.
The new error model is applied to all endpoints.
The case with showing - "Cannot change the document because it's changed on another device", is working for all type of modification on document. Same for user-profile.
There is no weird or missing error messages - for example if we trying to trigger "already created" error when creating document, it shows such message.
The errors that are triggered after certain interactions - like already exists, invalid field or others - are displayed correcly.
The error - generic one, when there is no internet, looks good too.
PS: Remember to clear added documents - permanent ones after testing.
Context
Currently, some of our endpoints use "old" error objects, while others use "new" error objects. This inconsistency creates challenges in reducing technical debt. We need to adopt the "new" approach for all endpoints.
DoD
PS: Remember to clear added documents - permanent ones after testing.