The discussion revolves around a bug in the ‘replace word/phrase’ functionality where the wildcard (*) does not correctly include the matched text in the generated link. emilio reported that se rver log* fails to include the ‘s’ in the link, unlike server log. sam acknowledged this as a bug, and nbianca explained that the wildcard uses regex and fixed the issue in a pull request. emilio initially experienced the issue again but confirmed it was resolved after a deploy, thanking sam and nbianca for the fix.
Trying out the new replace word/phrase functionality but am unclear how the wildcard works in the case below.
I wanted to replace server log with a url to info on how to get logs. It nicely leaves the word and creates a link. So I tried to use server log* to also cover server logs but the link created does not include the wildcard. Not a huge deal just a bit weird looking. is there a way to make it include the S. Image of what I mean
The wildcard character makes the use of regular expression necessary when matching, no matter what the value of watched_words_regular_expression is. This is because * is converted to \S*. I fixed the problem in:
Not sure if this was pushed to production but I edited ours to include the * again and now all of ours that have the wildcard will not create the link but the ones without the wildcard it will