![]() ![]() the property name will now be the same minus the forward slash which is causing the trouble.īut in the code above only the first JSON object in the request body will actually be parsed. In order to do the replace you will first need to JSON.stringify (response) then do your JSON parse on responsenew. Response body download can t parse JSONĭo a replace on the entire string removing the slash before replacing it. ![]() The stack trace provided by the browser is focused on the JSON.parse() handler within Angular itself, as this is where the XHR response is actually being processed. This solution works for us and we are using the block editor without encountering the JSON response error. In this event, press Ctrl + S (Cmd + S for Mac) to manually save your changes. However, it could be that the editor fails to automatically save your changes. You should not encounter the JSON response error. Because of the error, the output to local storage function on the browser is not performed. So Swagger-UI outputs the "can't parse JSON" message. Swagger-UI runtime response handler determines whether the response is valid. The sending server is incorrectly configured. The response is actually a text file - not JSON. However, when accessing the service from an external system, the double quote in the response data is not decoded. When accessing the JSON response which includes double quotes (") from the Pega application, the double quote is decoded and a valid JSON response is got. Service REST is created such that it returns a JSON response. That was the reason why can't parse json was thrown. ![]() If more than json data is returned, it must be contained in json array. This has no impact on flow insertion.Īnswer is found. Swagger UI is trying to parse an empty Json response and fails. But UI returns an error in response body with a response code of 201 (created). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |