Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce debug groups, for more precise debugging #2611

Closed
danielbachhuber opened this issue Mar 30, 2016 · 0 comments · Fixed by #2648
Closed

Introduce debug groups, for more precise debugging #2611

danielbachhuber opened this issue Mar 30, 2016 · 0 comments · Fixed by #2648

Comments

@danielbachhuber
Copy link
Member

--debug is intentionally verbose - if you're trying to debug an issue, you want as much information as you can get.

But, you don't necessarily need all of the information all of the time. We should introduce a second argument to WP_CLI::debug() to permit grouping of debug statements. For instance, we could use WP_CLI::debug( $message, 'bootstrap' ) to group all of the bootstrap debug, and WP_CLI::debug( $message, 'command' ); to group command debug.

Usage would be --debug=bootstrap. Using it as a flag would follow existing behavior of displaying everything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant