<...>
I’ve encountered that a few times when publishing some sql code here. Normally it was only down to one command (not always the same one), so what I did was apply a dicothomic approach (*) to locate the command that was making the error appear. I then substituted the command for a "sweet command" (i.e. "order by" for "ordenar by"), and put a note at the foot of the post to indicate the necessary swap to the code to be correct.
Nevertheless, if the code is long, and there are multiple key words that cause the issue, it may be a bit cumbersome with the above approach.
(*) i.e. publish half of the code, and see it it displays properly, if not, publish a quarter of the code, and see if it displays, and so forth. That allows you to delimit the problematic commands by applying a dichotomic approach.
for (const game of existingGames) {
const wager = game.game.wager / 100000000;
html += "<div>Game between " + game.game.players[1] + " and " + game.game.players[2] + " for " + wager + runtime.globalVars.Symbol + " (<a href='#' onclickityclick='parent.postMessage(\"" + game.address + "\", \"*\"); return false'>Watch</a>)</div>";
}for (const game of ourGames) {
const wager = game.game.wager / 100000000;
html += "<div>Game between " + (game.game.players[1] === runtime.globalVars.ValidatedAddress ? "you" : game.game.players[1]) + " and " + (game.game.players[2] === runtime.globalVars.ValidatedAddress ? "you" : game.game.players[2]) + " for " + wager + runtime.globalVars.Symbol + " (<a href='#' onclickityclick='parent.postMessage(\"" + game.address + "\", \"*\"); return false'>Watch</a>)</div>";
}
Replace "onclick" for "onclickityclick" or whatever, and explain the necesary change outside the code area ...
