Skip to content

Documentation: Missing SYNOPSIS in App::Cmd::Subdispatch (rt64299) #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rjbs opened this issue Feb 1, 2013 · 1 comment
Open

Documentation: Missing SYNOPSIS in App::Cmd::Subdispatch (rt64299) #17

rjbs opened this issue Feb 1, 2013 · 1 comment

Comments

@rjbs
Copy link
Owner

rjbs commented Feb 1, 2013

https://rt.cpan.org/Ticket/Display.html?id=64299

I know in principle what A::C::S is supposed to do, but I have no idea
how to use it in my code. Even just a single example would help...

Mark.

Mark Lawrence

@jayallen
Copy link

Yeah, I actually pored through the tests to find out and—after a massive number of issues caused, I think, primarily because I was also using a base command class in addition to a nested command—I finally did...but then I ran into #35 and gave up.

It would be great to see:

  1. Better docs around this including examples of using a base command class in addition to a subcommand
  2. Support in App::Cmd::Setup for subdispatch to keep things consistent
  3. Fixing subdispatch commands are promoted to top level commands #35 because the current display of subcommands is too confusing to unleash on users
  4. Examples of using subcommands with the same names (e.g. myapp foo list and mysql bar list) which gave me errors because of duplicate command names (though I admit without good documentation I may have been doing it wrong)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants