PR testing should validate ts() strings
PR review sometimes catches incorrect uses of
ts, but not always. The gettext extraction scripts are pretty good at catching many invalid use-cases.
It would be nice to have to run string-extraction on pull-requests. Technically, it should be a quick check to add, similar to checking code syntax.
One issue we have, is that there are many 20-25 errors that are systematically thrown by the string-extractor. Some are annoying to fix issues, others are incorrect uses of 'ts' that are difficult to workaround.
It would be really useful to have a way to flag tolerated or known-issues, so that we can at least start applying some checks moving forward.
Worst case, it could be a list of regexs of code to ignore?