Skip to content
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

Please add .command() function a path config #481

Closed
winys opened this issue Dec 23, 2015 · 5 comments
Closed

Please add .command() function a path config #481

winys opened this issue Dec 23, 2015 · 5 comments

Comments

@winys
Copy link

winys commented Dec 23, 2015

It would be better if we can customize the path of sub-command file.

@dszakallas
Copy link

Our naming policy enforces camel case for filenames, but subcommands are more naturally written in kebab case. Currently commander doesn't do this mapping neither gives an option for me to do it manually. It would be great if there would be either

  • camelize option for subcommands or
  • a way to configure the executables` path.

@shadowspawn
Copy link
Collaborator

shadowspawn commented Apr 26, 2019

Pull Request #854 adds an option for this.

I am interested in feedback on executableFile as the option name?

e.g.

program
.command("example", "example description", { executableFile: "myExampleCommand" });

@shadowspawn
Copy link
Collaborator

shadowspawn commented Jul 21, 2019

Pull Request #999 is being considered for v3, adds option to override executable file name

@shadowspawn
Copy link
Collaborator

This issue will be resolved when v3.0.0 is released. Available now as a prerelease. See #1001

@shadowspawn
Copy link
Collaborator

.command now supports the executableFile option (thanks to @abetomo).
Shipped in v3: https://github.com/tj/commander.js/releases/tag/v3.0.0

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

3 participants