Last Updated: 27 Nov 2023 10:37 by Niko
Imported User
Created on: 18 Sep 2017 05:39
Type: Feature Request
Bug in JSON rendering - empty arrays don't display
I've attached the raw HTTP response, copied directly from Fiddler. At lOperations[0].lRecords, you'll see that there are 2 records (arrays) and that each record contains 6 items, the last of which is an array. However, when I view the resonse using the JSON filter, the second of these arrays appears to contain only 5 items. I'm sure that the bug has something to do with the fact that the sub-array in the second array is an empty array, but it should display as an empty array, not as if it weren't there at all.
Posted on: 27 Nov 2023 10:37

Has this been fixed in a newer version yet? I'm working on code again that sends JSON back and forth and if the JSON panel can't be trusted, it's going to be a lot more difficult to find out what's happening

Nick Iliev
Posted on: 23 Nov 2021 08:44

Hello Niko,


Thank you for providing the additional details and the sample response. This sounds like a legit feature request, so I am moving it from a bug report to the FR section, and the team will consider it for future releases.

As a side note, I want to mention that the new Fiddler Everywhere is using Monaco editors, and the above case is handled as expected (see the attached screenshot).

Nick Iliev
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.

Attached Files:
Posted on: 23 Nov 2021 07:53

Also, see attachment for how FireFox renders the same JSON. Very intuitive. I recommend taking inspiration.

Attached Files:
Posted on: 23 Nov 2021 07:50

Here is an example:

    "Text""Hello World",
    "EmptyObject": {},
    "EmptyArray": [],

See attached screenshot for behavior.

Attached Files:
Posted on: 22 Nov 2021 20:49
Supplying an example of the problematic JSON would be useful.
Posted on: 18 Nov 2021 10:26

Goddamnit, I just wasted upwards of 2 hours trying to find out how some legacy code could possibly produce some JSON where parts are missing, because of this exact issue.

I also can't imagine a situation where this would be useful in the first place. Please fix this.