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
My first reaction is that it does make sense, but it might not be as easy or straight forward.
For one thing, what would the alias define? long or short? Or would it allow an array of aliases?
I think it can be added easily. I have started a codex session, I hope I can get it into a 1.4.0.rc3 version today or tomorrow.
For the help string, I am thinking of simply showing all the options:
--container, -c, --pod, -p NAME
Help string here
instead of
--container, -c NAME
Help string here
Aliases: --pod, -p
If you have any strong opinion one way or the other, let me know - I am open to both options, but the first is slightly easier (no custom strings involvement, easier for usage texts on error etc)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hello,
I'm using --alias for commands, and i think it would be useful to be able to do the same for flags, as I understand it is not possible right now.
Example:
My CLI supports a command with
containerand has alias forpod. I have a flag--containerfor which I would like to set an alias to--podWould that make sense ?
All reactions