standardize regexps for code signatures

[eighthave]

Right now the code signature regexp are basically all words separated by . Since . matches anything, this could lead to false positives, e.g. the regexp com.here would match com.here and comehere. Code signature printing methods generally use either . or / as the separator, so using [/.] would be the most accurate. Otherwise if there are other potential chars used as separators, using \W ("non-word chars") would be better than .

[eighthave]

@pnu-s I think you mentioned you were going to do a mass edit on this directly in the database. Using [/.] would be best IMHO.

[pnu-s]

@eighthave You're right, we discussed this but I did not take the time to do so yet.

I need to make sure this won't break anything by making a couple of tests but I agree with your proposal.

[jawz101]

yes please. I never know how thorough of a regex expression to use.

ads.advertising.com
sdk.advertising.com

^.*.advertising.com$

or just a string search of the advertising domain so it grabs all advertising.TLD? I guess I just leave it to you all to change and we just give you realworld examples in the box

[eighthave]

I think the regex should be as specific as possible, since false positives seem more likely than false negatives in this case. I think the `^` and `$` are assumed, or put another way, it is fed into a Python `re.match()`