envy
envy copied to clipboard
:angry: Environmentally friendly environment variables
Hi! I'd like to know what is the proper way to group multiple independent env vars prefixed with a component name into a Haskell component structure that represent the component...
Parsing a bool variable, not only does `"true"` not work as a value, but the error message is not helpful in finding out that I should specify `"True"`: ``` Parse...
The example at the top of http://hackage.haskell.org/package/envy-2.1.0.0/docs/System-Envy.html and the last one in the README using `DefConfig` don't work. I get "Variable not found" errors, when the docs claim it defaults....
It'd be nice to be able to quickly produce a list of generated environment variable names being used, when one makes an instance of [`FromEnv`](https://github.com/dmjio/envy/blob/e93904f2128cbbed100c9847377f9e3407658707/src/System/Envy.hs#L179) for a type that has...
For more parse failure information, we should use the latest and greatest `readEither` function from `Text.Read.readEither`.
[envMaybe](https://hackage.haskell.org/package/envy-2.1.0.0/docs/System-Envy.html#v:envMaybe) indicates that it will return `Nothing` if the environmental variable is not set, but it **also** returns `Nothing` if the environmental variable is set but is not parsable into...
Problem ==== - Handling `Maybe` values in the `Parser` monad is troublesome. - Even `envMaybe` mixes up variable-not-found-error with others, which makes the difference of `Nothing` and `Left String` obscure....