Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Cannot escape search operators #3867
Setup and configuration
While the documentation claims that search comparators can be escaped:
they apparently cannot. This is probably a regression.
If this gets fixed, I think all search operators (also
A bug/issue report contains a clear, concise description of an issue. It is not my job to go around looking at links and try to interpret the intent or issue. Links are there to make references and clarify things, even help demonstrate an observation but the issue report needs a clear description of what has been observed by the reporting person as in: "The documention says  ".... " that white-spacing can be used in case of ... such as
This not a regression to the previous release. In fact, there is no test that covers this use case and despite the description in the documentation " ... can handle those cases, value notations are white-space sensitive. To avoid confusion a space is inserted after :: ..." I would not support white-spacing as escaping pattern. There is an established
As for the matter of white spacing (untrimmed) the following may (haven't tested this) require a change to avoid trimming a "chunk".
But you would we need additional changes to keep avoiding
Same as above, for any one interested in implementing this, use