Add support for watchdog:show --exclude-type

[gitressa]

Is your feature request related to a problem? Please describe.

If you have installed a Drupal site in another language than English, you may get a lot of "English translation file not found" errors for all contrib modules (for example https://ftp.drupal.org/files/translations/all/metatag/metatag-2.0.2.en.po.) at every Cron run.

See Drupal install throwing "Translation file not found" notice for "en" langcode when "translate_english" is set to false.

These false positive entries can fill up the database log, and thereby drush watchdog:show output.

Describe the solution you'd like

As a workaround, it would be nice to be able to exclude a type. For example:

drush watchdog:show --exclude-type=locale    Exclude messages of type locale

This could also be a nice feature for example for Cron, which has a lot of entries.

Describe alternatives you've considered

You could enter all the other types, but that is clunky.

[weitzman]

You want Drush's output filtering feature. It is criminally underused. This use case is solved by drush watchdog:show --filter="type!=locale". A lot of options in watchdog:show could alternatively be done with output filters.

[weitzman]

Anyone is welcome to add another Example in Help with this info.

[gitressa]

Thanks for making me aware of the output filter in Drush, that is indeed very cool!

I created an MR, which adds your example to the list of Watchdog help items, since that command is one where the filter feature can often be useful.

[gitressa]

Thanks, very fast! I just re-read the sentence, and realized that the filter feature, which is the main character here, is not mentioned ... Perhaps this would be better?

Now:

Exclude rows via the negation operator !

Better?

Exclude rows with the filter feature, via the negation operator !

[weitzman]

Yes, its better. I have some sad news to report tho. Drush is moving even further toward a native Symfony Console setup and these example descriptions may be a casualty. See symfony/symfony#45050

[gitressa]

Losing the examples under each Drush command would definitely be a setback ... it's so great to have them available right there when you need them.

I hope, since Drupal and Drush are big players (I assume) in the Symfony world, that they may help steer Symfony in a direction where some kind of help feature can stay available in Drush.

[gitressa]

Oh, and about the little improvement, should I make a new PR, or can you do it directly?