Case sensitive short form

[danvirsen]

Hi!

I migrated to ff a good while ago but one thing that I really miss from our old solution is the possibility to have case sensitive short forms for flags.
As an example, we take in a "min" and "max" value in an application. Previously we accepted these as -m, --min and -M, --max which felt nice and intuitive. I had to switch that to -n, --min and -m, --max which doesn't make much sense to me.
After checking a couple of cli tools it seems like case-sensitive short-form flags and option names is the norm.

The error message also still has the casing.

Error: -M, --max: duplicate flag (-m, --min)

Would it perhaps be solved automatically if only long-form flags were allowed in config files and environment variables, like we touched on here #130 (comment)?

What are your thoughts on this?

[ardnew]

Just ran into this same issue with -v, --verbose and -V, --version.

I've added an option to ignore short flag names (for env lookup only, not config files), and it does indeed seem like a reasonable fix for case-sensitive short form.

Of course, you still have a conflict if, for example, you define -f, --foo and -F, --FoO. But, in that case, you probably deserve a broken tool.

See the changes here: main...ardnew:ff:feat/case-sensitive-flags

[peterbourgon]

Happy to review a PR to change env var lookups to only consider flag long names. That PR would also need to update .env config file parsing to have the same behavior, and also update the existing e.g. fftest tests to re-define the e.g. Vars flag names with long names instead of their current/default short names, so that the existing test(s) continue to pass.

[peterbourgon]

Should be fixed by #153, let me know if it works for you.

[danvirsen]

Works great, thanks! :)