Fixed subcommand registration, namespace, and package files.

[sun]

Objectives

• Register as subcommand wp db export-clean
  • https://github.com/netzstrategen/wordpress-core-standards/blob/master/src/Commands/UserExport.php works, but this here does not yet. ⚠️ Not clear why. Maybe the db command is registered specially in the WP-CLI bootstrap?
• Ensure the name is consistently "export-clean" and not some other order or variation of it.
• Correct the namespace.
• Correct the package information.
• Correct the hook names.

[sun]

The subcommand registration should be simple as that - as documented in wp-cli/wp-cli.github.com#269 and wp-cli/wp-cli#1767

Further resources

• https://make.wordpress.org/cli/handbook/references/internal-api/wp-cli-add-command/
• https://wordpress.stackexchange.com/questions/331861/creating-a-subcommand-for-custom-wp-cli-command

[sun]

Updated for the committed vendor packages. Ensure to use composer dump --optimize to generate the autoloader in that case.

[sun]

The subcommand works correctly when registering for the user command instead of the db command. The db command seems to be registered in a special way.

diff --git a/plugin.php b/plugin.php
index d2cc886..8ede851 100644
--- a/plugin.php
+++ b/plugin.php
@@ -26,4 +26,5 @@ include_once __DIR__ . '/vendor/autoload.php';
 
 add_action('cli_init', function () {
   WP_CLI::add_command('db export-clean', __NAMESPACE__ . '\CliCommand');
+  WP_CLI::add_command('user export-clean', __NAMESPACE__ . '\CliCommand');
 });

[sun]

wp-cli/wp-cli#5274 might be a relevant fix.

The registration of db and user commands appears to be the same:

• https://github.com/wp-cli/db-command/blob/master/db-command.php
• https://github.com/wp-cli/entity-command/blob/master/entity-command.php

The commands themselves, too:

• https://github.com/wp-cli/db-command/blob/master/src/DB_Command.php
• https://github.com/wp-cli/entity-command/blob/master/src/User_Command.php

One difference is this directive on the DB class:

 * @when after_wp_config_load

It causes the db commands to skip most of the WordPress bootstrap:

• https://github.com/wp-cli/handbook/blob/master/internal-api/wp-cli-add-hook.md
• https://github.com/wp-cli/wp-cli/blob/7914bc4fdd5461da83da10358e36dcecd4444cc2/php/WP_CLI/Runner.php#L1245

Therefore, WP-CLI dispatches to the db command very early in the bootstrap (visible when running with --debug). At that point, only wp-config.php has been loaded, but no must-use plugins yet.

The solution is to restore the wp-cli.yml in the project root to load the additional command in the early WP-CLI bootstrap:

require:
  - wp-content/mu-plugins/wp-cli-db-export-clean.php

And also override the bootstrap level for the export-clean command (class method) to load the whole WordPress environment:

   * @when after_wp_load

Just committed those changes.