Handle windows carriage returns (CRLF) in Filter form

[alexiswl]

Hello,

Whenever I copy multiple lines from my IDE into the jqplay services url, I would get this error

unexpected INVALID_CHARACTERm expecting $end

I did a bit of debugging locally and discovered that when I copy from my clipboard on Windows 10 into a Microsoft Edge browser (version 105.0.1343.50) that the line endings are ascii characters 10 + 13, as opposed to just 13.

If I remove the line endings and then recreate them inside the Filter form, everything is fine

This doesn't happen when I do the same thing in Firefox so seems to be OS/browser specific.

I did try stripping the CRLF line endings in the GO source code but don't know enough about the GO language to know exactly where this snippet needs to be put.

[generalmimon]

I've just hit this issue in Chrome. The worst part about it is that if you don't know about it, you have absolutely no clue what's happening and what's wrong with the perfectly valid-looking jq command (because the error is in an invisible character). So I guess this may be quite puzzling for many people.

And I don't think it occurs that rarely - yes, it doesn't happen when you write the jq command directly in the "Filter" field in the browser. But once you're writing some more complicated jq filter, chances are you'll want to start by copying a prepared jq filter from somewhere (some text editor, etc.), which is where you're quite likely to run into this issue, because the CR LF line endings are default on Windows.

You can check the presence of CRLF endings for example by pasting the clipboard contents to a hex editor like HxD. If you see 0d 0a somewhere in the hex view, that's a CR+LF sequence; an isolated 0a is a LF ending.

This doesn't happen when I do the same thing in Firefox so seems to be OS/browser specific.

I can confirm this doesn't happen in Firefox - apparently Firefox sanitizes the input you copy in the "Filter" field by replacing the CR LF endings to just LF. Chrome doesn't do this and sends the jq expression unchanged (with \r\n, if it was present in "Filter" field), which isn't accepted by the jq on the server (and it responds with the error error: syntax error, unexpected INVALID_CHARACTER, expecting $end as we saw).

---

I did a bit of debugging locally and discovered that when I copy from my clipboard on Windows 10 into a Microsoft Edge browser (version 105.0.1343.50) that the line endings are ascii characters 10 + 13, as opposed to just 13.

You have the ASCII codes the other way around - you actually meant 13 + 10 (13 is CR and 10 is LF; it can be written as 0d 0a in hexadecimal, or in many programming languages in string literals using escape sequences as \r\n), as opposed to just 10 (0a, \n, LF).