You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now parsing the environment variable process is failing fast. That's mean that only first uninitialized env is printed. If you have 5 environments variable then you can even need to execute the application 5 times to get info about all variables. I know that every application should have proper documentation but still, IMO it will be super useful to have an option to change that behavior and print all unset environment right after the first execution.
Details
Assumption that app has the following config:
typeConfigstruct {
DebugboolClientIDstring
}
and user didn't provide both envs.
Current solution
Output:
envconfig: keys DEBUGBB, DEBUG_BB, debug_bb, debugbb not found
I'm on the fence on this. On one hand I think it would be relatively useful, on the other hand I'm not sure it's worth it for a use case which will in my opinion be limited in scope.
I'm also not sure if it's worth complexifying the code for this. If it doesn't require modifying a lot of code I'll be more willing to merge it but I'm not sure.
Do you already have an implementation ready that I could review ?
Description
Right now parsing the environment variable process is failing fast. That's mean that only first uninitialized env is printed. If you have 5 environments variable then you can even need to execute the application 5 times to get info about all variables. I know that every application should have proper documentation but still, IMO it will be super useful to have an option to change that behavior and print all unset environment right after the first execution.
Details
Assumption that app has the following config:
and user didn't provide both envs.
Current solution
Output:
Desired solution
Add new option param
Output:
I you will agree with me then I can also provide the implementation for that.
The text was updated successfully, but these errors were encountered: