-
-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relax constraint on env_prefix when reading from environment #145
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also please add a v4.11.0 (2022-07-??)
section in the changelog with two entries, one in Added
describing the new feature and another like
Lines 84 to 86 in 593dd78
Deprecated | |
^^^^^^^^^^ | |
- ``logger`` property will no longer accept ``None`` in v5.0.0. |
Reading parameters from environment is a great feature, but user can sometimes want to not have any prefix when reading environment variables. This patch updates the property env_prefix to accept boolean, so that if set to True, if won't prefix the read environment variables.
Kudos, SonarCloud Quality Gate passed! |
All tests/checks pass. But I'm not sure to understand why Windows 2019 test fail with
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now all looks good. The failing tests are due to the changes I did and not related to this pull request.
Reading parameters from environment is a great feature, but user
can sometimes want to not have any prefix when reading environement
variables.
This patch introduces another parameter named empty_env_prefix,
that if set to True, will initialize env_prefix to None, and hence unlock
what has been described above.