Was previously attempting to cast directly from []interface{} to
[]string or []int which Go doesn't support. Instead, we iterate over and
cast each value (error'ing if the value is not the correct format).
Fixes#580
Sorry, forgot to add imports correctly, needed to edit the file and make the commit using the github online editor, since I can't access from my current location from git.
The funtion `loadDataFrom` does not take care of Windows users since any of the conditions met and it returns an error.
The change looks for the runtime where it's running and then if the filePath contains a `\`
Sorry, forgot to add imports correctly, needed to edit the file and make the commit using the github online editor, since I can't access from my current location from git.
The funtion `loadDataFrom` does not take care of Windows users since any of the conditions met and it returns an error.
The change looks for the runtime where it's running and then if the filePath contains a `\`
Currently cli silently (aside from IntSlice and Int64Slice which oddly
printed directly to the error stream) ignores failures that occur when
parsing environment variables for their value for flags that define
environment variables. Instead, we should propogate up the error to the
user.
This is accomplished in a backwards compatible manner by adding a new,
internal, interface which defines an applyWithError function that all
flags here define. In v2, when we can modify the interface, we can drop
this secondary interface and modify `Apply` to return an error.
When assigning values to flags (also when interogatting via
`context.(Global)IsSet`.
For boolean flags, consider empty as `false`.
Using `syscall.Getenv` rather than `os.LookupEnv` in order to support
older Golang versions.
Jesse Szwedko
Antonio Fdez
HIROSE Masaaki
Péter Szilágyi
Joe Richey
Maximilian Meister
Bo-Yi Wu
Dan Buch
Kasey Klipsch
Joshua Rubin
drekar
mh-cbon