Jon Sequeira
Jon Sequeira
Sorry for the confusion. I ran your sample code the other day and my test runner swore to me that it passed but it must have had its fingers crossed...
Which libraries would you like to see this for? It's best to open more specific issues so they can be tracked separately.
Related: #1125
As I posted on #969, it's not clear to me that we should do this. Command lines are typically case sensitive on Linux/macOS, and often on Windows as well. Could...
I think the previous comments assumed this would be an end user decision and not a developer decision. I think each approach has its own problems. For example, possible ambiguities...
> each alias should be defineable as case-sensitive or not, so that single-character aliases can be case-sensitive in their crowded space, but long verbose commands don't need to be. You...
I suspect that allowing some commands to be case insensitive while others are case sensitive would make a CLI harder for the end user to understand and learn so I...
Question for everyone on this thread. Per the suggestion made by @Kaelum above, would case-insensitive commands meet your backward compatibility needs, or are case-insensitive options also needed? If the latter,...
> For options, I have never seen, nor expected, that "--" (double dash) options be case-insensitive. @Kaelum `--`-prefixed options tend to be found in POSIX-style command line apps, which are...
> Do you intend for PowerShell module creators to use this? Because PowerShell is so different when compared to all other command lines, I am not sure if it is...