Imagine you have a rule in your abuse filter like ... ccnorm(added_lines) rlike .... There is no direct way to debug this currently, and you just have to read the documentation to venture a guess as to what the output of that function would be for a particular edit. This makes testing rules very difficult.
The solution I want to propose is this:
- Allow assigning the output to a custom variable (... debug := ccnorm(added_lines) { ...)
- When looking at the "details" view of abuselog (may it be for a previous edit that triggered a filter, or when using the examine page for batch testing), in addition to the built-in variables (like added_lines) whose value is shown in the table, also show the value of all custom defined variables.
This way one can clearly see what the output of that function was, and more easily debug the filter.