Suppose you have an app that supports right-to-left (RTL) languages, such as Arabic. In that case, the chucker app will also be RTL, which can sometimes hinder the readability of the response, especially if it is a large JSON. You depend on indentation to locate certain values for debugging purposes or to confirm that specific values have been received. For that reason, I suggest this change.

That's a good point, but maybe the header section on top should still respect the RTL? I'm not a RTL native so I can't make a good call here.

Suppose you have an app that supports right-to-left (RTL) languages, such as Arabic. In that case, the chucker app will also be RTL, which can sometimes hinder the readability of the response, especially if it is a large JSON. You depend on indentation to locate certain values for debugging purposes or to confirm that specific values have been received. For that reason, I suggest this change.

That's a good point, but maybe the header section on top should still respect the RTL? I'm not a RTL native so I can't make a good call here.

It also doesn't help @cortinico. As a native Arabic speaker, it would only help if the information were in Arabic. Since it is in English, it makes sense to keep it in the same direction because it follows the key: value format, like date: 12/04/1997. It would help if it were 12/04/1997: تاريخ, but it isn’t, so it makes sense to have it as it is for all languages.