Formatting of Unicode-encoded characters leads to broken JSON output

[jabrandes-bscm]

When having a JSON string as input, i.e. from an API response in Bruno, it seems that unicode-encoded characters from embedded JSON content in string fields are decoded in the final formatted JSON, which may lead to the output of invalid JSON that fails proper parsing.

Tested with Version: 0.4.0

Example:

A JSON-string of the form:

{
    "myEmbeddedJson": "{\u0022embeddedField\u0022:\u0022embeddedValue\u0022}"
}

Current Output:

{
    "myEmbeddedJson": "{"embeddedField":"embeddedValue"}"
}

(Note the previously encoded quotes from the embedded JSON now being unencoded first-level quotes.)

Expected Output:

Either:

• same as example input (resembles the input more closely if existing escape-sequences are kept as-is)
• with Unicode-encoded characters replaced by their respective direct escape-sequences, if defined (i.e. \u0022 to \", see RFC-38259, Section 7; example output below)

{
    "myEmbeddedJson": "{\"embeddedField\":\"embeddedValue\"}"
}