Add missing support for command-arguments to commands added with .addCommand()

[aweebit]

Problem

const { Command } = require('commander');

{
  const program = new Command();
  program.command('sub <arg>').action(arg => console.log(arg));
  program.parse(['sub', 'arg'], { from: 'user' }); // arg
}

{
  const program = new Command();
  const sub = new Command('sub <arg>').action(arg => console.log(arg));
  program.addCommand(sub);
  program.parse(['sub', 'arg'], { from: 'user' }); // error: unknown command 'sub'
}

Solution

Move declared command-argument parsing from .command() to constructor.

ChangeLog

Fixed

• added missing support for command-arguments to commands added with .addCommand()

[shadowspawn]

I was considering this PR and the related changes, and realised I do not want to change the parameter to createCommand() to include args. Working backwards, I do not want to change the Command constructor.

This is a long-standing behaviour, and is now somewhat less of an issue. The more recent and now somewhat preferred way of adding arguments is using .argument(), which is also the way to add an argument description if desired.