mhcg/monolog-wp-cli

Extension for Monolog to support outputting to WP-CLI (The WordPress command line interface) when running wp command lines.

monolog-wp-cli's Issues

Add documentation to the Wiki explain how the WP-CLI quiet and debug options work

Would be useful to clarify how the --debug and --quiet options in WP-CLI effect the logging done by the handler.

Travis CI builds failing with various PHPUnit issues

Describe the bug
Essentially looks like PHPUnit 8 is being used for all version of PHP which was never going to work.

Additional context (Optional)
https://travis-ci.com/mhcg/monolog-wp-cli/builds/141622078

Provide basic PHP 8.x support

Describe the solution you'd like
Updating the composer PHP version from "php": "^7.2", to "php": ">=7.2", would at least allow this to be installed on PHP 8.x systems.

Additional context (Optional)
None

CI build failing on PHP 7.3 RC

Describe the bug
Doesn't currently build on PHP 7.3 RC due to some composer dependencies that probably aren't needed anyway.

Additional context
On reflection, was silly to include some of the packages like lint and sniffer as they are nothing to do with the build process or indeed the functionality of the project. Should take them out and keep composer.json lean as possible.

https://travis-ci.com/mhcg/monolog-wp-cli/jobs/152433096

Fix "method_complexity" issue in src/Monolog/Handler/WPCLIHandler.php

Function write has a Cognitive Complexity of 10 (exceeds 5 allowed). Consider refactoring.

https://codeclimate.com/github/mhcg/monolog-wp-cli/src/Monolog/Handler/WPCLIHandler.php#issue_5bc1d56ee5ea0d0001000012

Fix various Code Scanning issues re Dockerfile

Only really used during dev, but still, be good to have the issues fixed.

Code Scanning Issues

`$logger->notice()` should be resolved to `WP_CLI::log` instead of `WP_CLI::warning`

Hi @markheydon, thanks for this little package! This is not really a bug, but rather a design question.

Regarding to the documentation of Monolog:

NOTICE (250): Normal but significant events.

This should not trigger a WP_CLI::warning, but rather just a simple WP_CLI::log:

$logger->notice('Something normal but significant happened');

What do you think? Happy to create a PR if you agree.

Unit test missing for verbose logging

Mini refactor of write() as well could increase the coverage to nearly 100%. Also see https://codeclimate.com/github/mhcg/monolog-wp-cli/src/Monolog/Handler/WPCLIHandler.php/source#issue-5ad54e79987697e28d4bafda610f12e1

Add ability to create an instance of WPCLIHandler with a custom logger map

The default logger map, mapping Logger methods to WP-CLI methods, should be more than sufficient for most uses. However, I can foresee some people may want to override the settings in some cases, for example, the ALERT level in the default has exit set to true. Maybe for some projects, this would be inappropriate.

The code was changed in commit 274f817 to support using an array for the mapping so shouldn't be a massive job now to allow a custom array to be used.