Is there a way to hide public class methods from WP CLI?

[hirasso]

Hi there! I'd like to know if there is a way to hide public methods from a class-based custom WP_CLI command.

I'm adding a custom command with subcommands like this:

\WP_CLI::add_command('my-command', new MyCommandClass());

The class contains various public methods that are being resolved to subcommands as expected. A reduced example:

class MyCommandClass {
    public function send_email(): void
    {
        wp_mail(
            $_ENV['LOGGER_MAIL_TO'],
            "Hello there!",
            "Hello again :)",
        );
    }
}

Now I need to overwrite the from header in this email. I'm using the filter wp_mail_from for this. But now the callback function is being listed as a subcommand, since it needs to be public (due to the way WP filters work):

class MyCommandClass {
    public function send_email(): void
    {
        add_filter('wp_mail_from', [$this, 'wp_mail_from']);
        wp_mail(
            $_ENV['LOGGER_MAIL_TO'],
            "Hello there!",
            "Hello again :)",
        );
        remove_filter('wp_mail_from', [$this, 'wp_mail_from']);
    }
    /**
     * Overwrite wp_mail_from
     */
    public function wp_mail_from(): string
    {
        return $_ENV['LOGGER_MAIL_FROM'];
    }
}

On the shell I now get this:

❯ wp my-command
usage: wp my-command send_email
   or: wp my-command wp_mail_from # I don't want this!

Is there a way to hide the filter callback wp_mail_from from WP_CLI?

[trepmal]

If you're not opposed to a closure, I think this could work.

\WP_CLI::add_command('my-command', 'MyCommandClass' );

class MyCommandClass {
	public function send_email(): void
	{
		$wp_mail_from = function(): string {
			return $_ENV['LOGGER_MAIL_FROM'];
		};
		add_filter('wp_mail_from', $wp_mail_from );
		wp_mail(
			$_ENV['LOGGER_MAIL_TO'],
			"Hello there!",
			"Hello again :)",
		);
		remove_filter('wp_mail_from', $wp_mail_from );
	}
}

[hirasso]

Very nice idea, thank you! I just wanted to make sure I wasn't missing anything in WP CLI's API.