-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
Teletype: inconsistent file naming in case a module's named with a dash #43
Comments
Also Or I suppose I should not name my application with a dash? |
Hi Xinyue, Thanks for trying the gem out. I would say that this a bug and I will look into it unless you have time to contribute? As far as executables go I cannot recall easily any Unix utility that has a dash in its name... I think if you were to have a dash, it would make it a bit difficult for people to use. However, it doesn't mean that this gem shouldn't support nested module names. I can imagine a situation where running new generator creates a different name for the exec file(even for single names): teletype new foo-bar-baz --name foo
teletype new bundler --name bundle |
Unfortunately I later figured out TTY was not what I'm going to use (I went to arguments style instead) but I thought I should still let you know if it's an unexpected behavior. A lot of tools have dash in their names. A different name for the binary is a good point. I can name it |
Again, thanks for raising the issue! Agree there are tools with dashes and it's totally up to you what you prefer. My preference is to stay away from long-winded and cumbersome names such as |
Fixed main cli generation to allow for namespaced application names 5312026 |
This is fixed |
I assume this is not correct.
The text was updated successfully, but these errors were encountered: