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
One can easily add the options add multiple options, which might be weird to do so, I would agree. But it is not documented what order will be used.
Should we either check for multiple options that should be mutual exclusively set?
Should we allow multiple options and make env_key to be the final resort, being explicitly set ?
I tend to go for the first solution, because it is the most easy. But I was about to start on #2, where I need multiple ENV-vars to be an option, to be able to deprecate without breaking people their stuff.
The text was updated successfully, but these errors were encountered:
One can easily add the options add multiple options, which might be weird to do so, I would agree. But it is not documented what order will be used.
Should we either check for multiple options that should be mutual exclusively set?
Should we allow multiple options and make
env_key
to be the final resort, being explicitly set ?I tend to go for the first solution, because it is the most easy. But I was about to start on #2, where I need multiple ENV-vars to be an option, to be able to deprecate without breaking people their stuff.
The text was updated successfully, but these errors were encountered: