René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Error details are not available","articleBody":"When a call to the content delivery API fails, the response contains a JSON object with details such as the error code, error message, and failed validation, as seen below:\r\n```json\r\n{\r\n  \"error_code\": 141,\r\n  \"error_message\": \"Failed to fetch entries. Please try again with valid parameters.\", \r\n  \"errors\": {\r\n    \"access_token\": [\r\n      \"Doesn't have access to specified environment\"\r\n    ]\r\n  }\r\n}\r\n```\r\n\r\nThe same call, when made through the SDK, provides none of the error information to the caller. The only response obtained is an `Error` object, with the HTTP status code as the error code and the status message as the error message, repeating the exact same information for the errors, resulting in something that could be seen as the following:\r\n```json\r\n{\r\n  \"error_code\": 422,\r\n  \"error_message\": \"Unprocessable Entity\",\r\n  \"errors\": {\r\n    \"errors\": \"Unprocessable Entity\"\r\n  }\r\n}\r\n```\r\n\r\nThat `Error` object completely discards the error details, making effective error handling impossible; there is no way to extract that information once the SDK calls back to user code. Contrast this with the SDKs provided for other languages. The .NET SDK parses the response JSON and uses those values to fill in the `Error` object. Is there any sort of plan for exposing the actual error details to the caller?","author":{"url":"https://github.com/feliperuiz","@type":"Person","name":"feliperuiz"},"datePublished":"2021-01-20T17:31:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/26/contentstack-java/issues/26"}