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
Describe the bug
Running this configuration:
[foo] match=":[1]" rewrite=":[1]" rule=""" where match :[1] { ":[_~foo]" -> true }, rewrite :[1] { ":[ _]" -> "|" }, """
Against the string one foo two three produces one | two three, whereas I would expect it to produce one|foo|two|three.
one foo two three
one | two three
one|foo|two|three
Interestingly changing the order of the match and rewrite fixes it. That is, changing the rule above to the following produces the expected output:
where rewrite :[1] { ":[ _]" -> "|" }, match :[1] { ":[_~foo]" -> true },
Also interestingly, using the original order but using a plain space character instead of the named whitespace matcher also produces the expected out:
where match :[1] { ":[_~foo]" -> true }, rewrite :[1] { " " -> "|" },
Reproducing
https://bit.ly/43kUxrz
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Running this configuration:
Against the string
one foo two three
producesone | two three
, whereas I would expect it to produceone|foo|two|three
.Interestingly changing the order of the match and rewrite fixes it. That is, changing the rule above to the following produces the expected output:
Also interestingly, using the original order but using a plain space character instead of the named whitespace matcher also produces the expected out:
Reproducing
https://bit.ly/43kUxrz
The text was updated successfully, but these errors were encountered: