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 would like an option to make the cli for the above program be ./entrypoint --some_name foo rather than ./entrypoint --some-name foo
Use case justification
As an opinionated full stack developer, I loathe automatic conversions between different 'case' styles for variable names. This kind of mechanism complicates simplistic code-base search mechanisms unnecessarily. Consider the reality of modern codebases -- where some command execution is embedded inside some terraform declaration as an arguments array that gets passed into a docker container -- or any other similar varieties of incidental complexity as arises when trying to use modern cloud providers. While building a company working on a product, I value increasing the likelihood that searching the codebase for some_name will find all-at-once the relevant ways in which the parameter is used as well as how the codebase deals with it. As such I would like the option to globally turn off the case conversions that typer does for both commands and options. I don't particularly care that the cli interface looks like ./entrypoint some_command --some_option vs ./entrypoint some-command --some-option as a user of a cli that is internally facing -- but I do want to achieve the quickest visibility into what some_option does within my system which includes: where the option gets passed, how the argument is depended on within the implementation, etc ...
Disabling mechanisms that produce needless aliasing would be useful to me to better achieve that end.
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
-
First Check
Commit to Help
Example Code
Description
I would like an option to make the cli for the above program be
./entrypoint --some_name foo
rather than./entrypoint --some-name foo
Use case justification
As an opinionated full stack developer, I loathe automatic conversions between different 'case' styles for variable names. This kind of mechanism complicates simplistic code-base search mechanisms unnecessarily. Consider the reality of modern codebases -- where some command execution is embedded inside some terraform declaration as an arguments array that gets passed into a docker container -- or any other similar varieties of incidental complexity as arises when trying to use modern cloud providers. While building a company working on a product, I value increasing the likelihood that searching the codebase for
some_name
will find all-at-once the relevant ways in which the parameter is used as well as how the codebase deals with it. As such I would like the option to globally turn off the case conversions thattyper
does for both commands and options. I don't particularly care that the cli interface looks like./entrypoint some_command --some_option
vs./entrypoint some-command --some-option
as a user of a cli that is internally facing -- but I do want to achieve the quickest visibility into whatsome_option
does within my system which includes: where the option gets passed, how the argument is depended on within the implementation, etc ...Disabling mechanisms that produce needless aliasing would be useful to me to better achieve that end.
Operating System
Linux
Operating System Details
This is not platform dependent
Typer Version
0.9.0
Python Version
Python 3.10.10
Additional Context
No response
Beta Was this translation helpful? Give feedback.
All reactions