Parameters from ENV about argu HOT 5 CLOSED

@haf It's just that I think using env vars for parameterization is ugly, violates referential transparency considerations and can be potentially dangerous. If completely unavoidable, I would rather just dereference the vars at the script level and pass through the CLI:

./myApp --foo=$FOO --bar=$BAR

If I am going depend on ambient state for configuration I would much rather have the ability to explicitly specify which aspects of that ambient state I want to use.

Suppose you are consuming an application that I wrote which uses Argu for environment variable parsing. Unbeknownst to you, my application is also looking for a $BAZ environment variable that triggers a functionality you're completely unaware of: let's say it drops the database it connects to once completed. Now, If you were to accidentally expose an export BAZ=true statement in one of your machines, this could carry potentially catastrophic consequences.

The above example by the way is inspired by a true story.

from argu.

I'm not the biggest fan of parameterization using env vars. That said, doing it is very simple; you just pass an implementation of IConfigurationReader to the ParseConfiguration method of your parser.

from argu.

Does the GetValue : string -> string return null if it doesn't have it?

Also, what about the #if !CORE_CLR at the top of the parsers? No parsing for .Net core or is it WIP?

Also, why aren't you a fan? I'm interested to know.

from argu.

from argu.

You got a PR from me!

from argu.