You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure why commander tries to require 'myscript'in the generated template when I specify 'myscript' as the "Machine name" - I would think that for most commander use cases you're not looking to load a gem with the same name as your script...
In addition, the ':version' is not set to something correct, but is instead set to Myscript::VERSION.
These 2 things prevent a stock generated script from actually running without erroring out.
I propose removing the require statement, and setting the default version to '0.0.1'. Also, I think the "Machine name" prompt is unnecessary. Wouldn't it make sense to just use the filename of the file passed in as the init argument?
Don't mean to sound negative, but these things just seem bewildering to me :)
The text was updated successfully, but these errors were encountered:
I agree with you, I'm not really sure why the original decision was made to set it up like that. I agree with your suggestions, and if you have the time to put together a pull request, that would be awesome...
I'm not sure why commander tries to
require 'myscript'
in the generated template when I specify 'myscript' as the "Machine name" - I would think that for most commander use cases you're not looking to load a gem with the same name as your script...In addition, the ':version' is not set to something correct, but is instead set to
Myscript::VERSION
.These 2 things prevent a stock generated script from actually running without erroring out.
I propose removing the require statement, and setting the default version to '0.0.1'. Also, I think the "Machine name" prompt is unnecessary. Wouldn't it make sense to just use the filename of the file passed in as the
init
argument?Don't mean to sound negative, but these things just seem bewildering to me :)
The text was updated successfully, but these errors were encountered: