We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CompleteSearch doesn't ignore escaped within-field-separator in fields with multiple items.
within-field-separator
Explanation:
subject
to
--within-field-separator=\|
--allow-multiple-items=to
Using the following TSV input:
subject to The \| subject \| value The \| to \| value
We get the following output from the server (parsed with jq):
{ "to": [ "The \\", " to \\", " value" ], "subject": "The \\| subject \\| value" }
The escaped \| are preserved in the subject field. The escaped \| are ignored in the to field and each | is interpreted as a separator.
\|
|
Is there another way to escape within-field separators? Otherwise it would be a useful addition.
Tested with Docker image https://hub.docker.com/layers/adfreiburg/completesearch/latest/images/sha256-bb8ca10e5dfb0ba433f8577e6220ad1cd6017e034b3c0ba84c68b0b6b8dae41b
The text was updated successfully, but these errors were encountered:
No branches or pull requests
CompleteSearch doesn't ignore escaped
within-field-separator
in fields with multiple items.Explanation:
subject
andto
.--within-field-separator=\|
in the Makefile.--allow-multiple-items=to
in the Makefile.Using the following TSV input:
We get the following output from the server (parsed with jq):
The escaped
\|
are preserved in thesubject
field. The escaped\|
are ignored in theto
field and each|
is interpreted as a separator.Is there another way to escape within-field separators? Otherwise it would be a useful addition.
Tested with Docker image https://hub.docker.com/layers/adfreiburg/completesearch/latest/images/sha256-bb8ca10e5dfb0ba433f8577e6220ad1cd6017e034b3c0ba84c68b0b6b8dae41b
The text was updated successfully, but these errors were encountered: