@killua99 Still interested in picking this up? Is something unclear about what the intended outcome should be?

Hi @schlessera sorry for delay this issue for so long, I've been committing patches in other place.

I would say, if anyone want to bring a patch for it, then it should be submit the path. I would do it just idk when if this week or the next one.

Is clear to me the scope of the issue and what the outcome should be.

Let's see if I've time for it soon™

I'm not quite sure how to really debug or test the debug flag here. Which situation would have such of thing? @schlessera

@killua99 An example of where this is being used is the core verify-checksums command.

• wp-cli/checksum-command gets loaded first, before wp-cli/core-command(alphabetical order)
• wp-cli/checksum-command contains core verify-checksums, however, when it wants to add this, the parent core command has not been registered yet. So it first registers the namespace core and attaches the core verify-checksums to that namespace. The namespace is a placeholder in that case.
• When wp-cli/core-command loads and wants to register the core command, it sees that there is already a core namespace registered. So it creates the core command, moves all the subcommands from the core namespace to the actual core command, and then replaces the core namespace with that new command.

This was fixed via #5563

Thanks for the effort in creating this PR, @killua99 !