SDK: Improved Error Handling in SDK Client Library

[fmontes]

Parent

28404

Task description

As a developer using the dotCMS SDK client library, I want to see informative error messages when there is an issue with a request, so that I can quickly identify and resolve the issue.

Acceptance Criteria

• The SDK client library should display clear and descriptive error messages when a bad request occurs.
• Error messages should provide relevant information about the issue, such as authentication errors or malformed requests.
• The error messages should be displayed in a user-friendly manner that helps developers understand the nature of the problem.

External Links

N/A

Assumptions & Initiation Needs

N/A

Quality Assurance Notes & Workarounds

N/A

[zJaaal]

IQA Failed

The errors are looking great but we have an [object Object] error that we should clean up, looks like at some part of the error bubbling the environment is expecting an string. We should show error messages effectively in the console and in the environment the code is running. Also in the 404 error maybe we could change the URL in the error message for path since the parameter is called path in the SDK

[object Object]

404

401

403

[KevinDavilaDotCMS]

I did the test and I can't see that error screen When an error occurs from the SDK, the NextJS application displays the errors like this

Browser:

Terminal:

[zJaaal]

I did the test and I can't see that error screen When an error occurs from the SDK, the NextJS application displays the errors like this

Browser:

Terminal:

IQA Passed

I tested it again and you are right! Looks like a cache thing.

[bryanboza]

Fixed, now we are able to get the corresponding error to every case, we receive the error status code and the correct message. However we are not doing anything at FE level in the provided examples, every one need to take actions in case of every error.

Tested on trunk [_2181d4a]