Support case insensitive command line options #116
Conversation
Adds a caseSensitive field to OptionDefinition to support parsing certain arguments in a case insensitive manner. The UNIX-based command line is traditionally case sensitive, but the Windows command line is not. The default behavior continues to treat all command line arguments as case sensitive.
|
@75lb , mind reviewing / allowing the CI to run? And let me know if I shouldn't check in those |
|
morning, thanks for the new feature - sounds good to me.. I will review it later today.. Yes, the |
|
hey @75lb , any updates? 🙂 |
|
Will you need the granularity of being able to set commandLineArgs(optionDefinitions, { caseInsensitive: true })Also, the general convention is to enable an option flag by setting it to |
|
Why are aliases always case-sensitive? Wouldn't it be more consistent to enable or disable case-sensitivity across the board? |
peazncheez
force-pushed
the
peazncheez/case-insensitive-arg
branch
from
86af4bf
to
e98c7be
Compare
Removes the usage of default parameter values
|
Hey @75lb , thanks for the feedback. I had originally implemented the per-option case sensitivity granularity since that would be most flexible, but it's not necessary for my use case and I agree the additional complexity likely isn't worth it. Pushed up some commits which:
|
De-linting.. minor doc updates
|
Merged and released in v5.2.0, thanks. 👍 |
|
Awesome, thank you! |
Case insensitive support was added to the command-line-args library in 75lb/command-line-args#116 and was released in 5.2.0. This commit updates the corresponding types.
…@peazncheez * Add types for case insensitive command line arg parsing Case insensitive support was added to the command-line-args library in 75lb/command-line-args#116 and was released in 5.2.0. This commit updates the corresponding types. * Remove tsconfig changes Co-authored-by: Bryan Williams <bwilliams@palantir.com>
Adds a caseSensitive field to OptionDefinition to support parsing certain arguments in a case insensitive manner. The default behavior continues to treat all command line arguments as case sensitive.
The UNIX-based command line is traditionally case sensitive, but the Windows command line is not. I'm working on a Windows application and we're currently using this library, but we'd like our args to be parsed in a case-insensitive manner.