I have the same issue.
I my scenario, I expect non-developers to be able to copy/paste JSON out of chrome dev tools into scenario/steps. This expectation is flawed, as it's asking far too much of the user to expect them to be able to prefix an addition double quote to a line of text, if that line of text starts with a double quote.
I would like to just have...
And the following JSON can be parsed
"""
{
"Hello" : "World"
}
"""
However, (as you point out, and for me to be verbose in my explanation) the first double quote before "Hello" is removed, and resulting in Hello" which is not valid JSON.
The only way I can get this to work is to add a double quote to the start of each line, or at the very least, just the ones that start with a double quote... so the following would work..
And the following JSON can be parsed
or
And the following JSON can be parsed
But given that our JSON is often up to ~100 lines long, it's not feasible (or efficient) to expect someone without basic DEV skills to craft the text/JSON around the double quote limitation.
Can I suggest an additional parser/convention be considered?