Item1379: command line topic specification may not work

I was going to play with a little profiling, and ran

• ./view AdminToolsCategory

and

• ./view topic AdminToolsCategory

and give me the Main WebHome.

which is quite wrong.

./view -topic AdminToolsCategory works, but ./view -topic AdminToolsCategory -skin plain does not.

-- SvenDowideit - 27 Mar 2009

I honestly can't figure out how one can expect to make that generic and working...

The only way I can think of is something along the lines of:

%args = @ARGV;
if( @ARGV % 2 ) {
    $topic = $ARGV[-1];
    delete $args{$topic};
}

And I'm pretty confident this will break loads of times

-- OlivierRaginel - 30 Mar 2009 You can -topic BlahBlah or topic=BlahBlah, which is probably already one style too many. ./view -topic AdminToolsCategory -skin plain works fine when I try it, as does ./view topic=System.AdminToolsCategory skin=plain. Sven, can you be more specific about why you think this doesn't work?

I don't like the idea of a default (unnamed) parameter. It makes the CLI parser more complex than it needs to be.

-- CrawfordCurrie - 03 Apr 2009

If this was urgent Sven or Crawford would have fixed it. We have had this for ages and it affects only command line use. Not a release blocker error.

-- KennethLavrsen - 19 Apr 2009

Several was against changing this. And no further actions from April to January. Obvious No Action case so we do not have this pilling up.

-- KennethLavrsen - 09 Jan 2010