Parsing string literals in predicates isn't accounting for `\s`

[DavisVaughan]

Parsing string literals in predicates isn't accounting for `\s`

[DavisVaughan]

Ah I think you're right! Swapping to \\s does fix the playground too.

So I think that may just be a small typo on the docs page where it needs to be \\s rather than \s, and then it makes sense to me that \n, \t, \r, and \0 are the only other ones handled specially.

[DavisVaughan]

Sure I'll do one monday!

[WillLillis]

Apologies if I'm mistaken, but it seems to work if you escape the slash before the s in your query.

Playground:

Query via CLI:

[maxbrunsfeld]

Yes, because we support escape sequences in those strings, you need to escape the backslash if you want to write a literal backslash (which you want in this case, so that the regex engine sees \s). Want to open a PR for the docs fix?