[Bug] Very agressive escapeing of characters when writing to file

[CrowbarToolsRobot]

Description

const jsonData = $convertToJSON[$$testing2];

function escapeNewlines(jsonString) {
return jsonString.replace(/\n/g, '\n');
}

const escapedJsonData = escapeNewlines(jsonData);

const parsedObject = JSON.parse(escapedJsonData);

const textValue = parsedObject.candidates[0].content.parts[0].text;

console.log(textValue);

Becomes:

const jsonData = {"candidates":[{"content":{"parts":[{"text":"!playMusic"}],"role":"model"},"finishReason":"STOP","avgLogprobs":-0.00043647171696648}],"usageMetadata":{"promptTokenCount":9181,"candidatesTokenCount":4,"totalTokenCount":9185,"promptTokensDetails":[{"modality":"TEXT","tokenCount":9181}],"candidatesTokensDetails":[{"modality":"TEXT","tokenCount":4}]},"modelVersion":"gemini-2.0-flash"};

function escapeNewlines(jsonString) {
return jsonString.replace(/n/g, '
');
}

const escapedJsonData = escapeNewlines(jsonData);

const parsedObject = JSON.parse(escapedJsonData);

const textValue = parsedObject.candidates[0].content.parts[0].text;

console.log(textValue);

When written to a file.

jsonString.replace(//\n/g, \\\n);
And
jsonString.replace(/\n/g, "\n");

Also fail.

Steps to Reproduce

1.Add the code into a write file effect, can replace $$testing2 with a JSON object.
2.Write to file
3.pro... uh bad code in file.

Expected Behavior

Escape characters get replaced very aggressively and break code blocks.

Firebot Version

v5.63.2

Submitted By

oshimia

Created via Discord.

[Oshimia]

I see phroggster has already made a commit for this, but it might be worth noting that this also seems to write newlines if text in a JSON string contains them. For example

{"candidates":[{"content":{"parts":[{"text":"Be... Patient? Kappa"}],"role":"model"},"finishReason":"STOP","avgLogprobs":-0.7294828097025553}],"usageMetadata":{"promptTokenCount":5321,"candidatesTokenCount":6,"totalTokenCount":5327,"promptTokensDetails":[{"modality":"TEXT","tokenCount":5321}],"candidatesTokensDetails":[{"modality":"TEXT","tokenCount":6}]},"modelVersion":"gemini-2.0-flash"}

Becomes:

{"candidates":[{"content":{"parts":[{"text":"Be... Patient? Kappa
"}],"role":"model"},"finishReason":"STOP","avgLogprobs":-0.7294828097025553}],"usageMetadata":{"promptTokenCount":5321,"candidatesTokenCount":6,"totalTokenCount":5327,"promptTokensDetails":[{"modality":"TEXT","tokenCount":5321}],"candidatesTokensDetails":[{"modality":"TEXT","tokenCount":6}]},"modelVersion":"gemini-2.0-flash"}

[phroggster]

I have deleted a comment of my own here that was not very helpful, and moved my commentary over to the Discord thread.

[Oshimia]

My text editor is Sublime text, so shouldn't be causing a new line on word wrap. I believe the issue was that the API I was using was adding a new line in the text response, which was being correctly ignored when Firebot processed the JSON natively, but would then get processed when I wrote to file, breaking the JSON structure. If I made a correct version of the JSON and saved it to a variable, then wrote that to file it would be fine, it was when I wrote directly from the effectOutput variable to a file that it broke. I don't think I ever tried saving it as a variable first and then writing it to a file though. I've attached a text file so you can see how the JSON was saved to the file.