Skip to content

Add support for parsing environment "None" strings to None. #206

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

Merged
merged 4 commits into from
Jan 10, 2024

Conversation

kschwab
Copy link
Contributor

@kschwab kschwab commented Jan 5, 2024

Resolves #199.

Adds support for parsing environment "None" type(str) to None type(None).

Copy link

codecov bot commented Jan 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4f24fad) 97.47% compared to head (dd39f9e) 97.61%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #206      +/-   ##
==========================================
+ Coverage   97.47%   97.61%   +0.14%     
==========================================
  Files           5        5              
  Lines         317      336      +19     
  Branches       66       71       +5     
==========================================
+ Hits          309      328      +19     
  Misses          6        6              
  Partials        2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Make sure that None type parsing is only applied to environment
variables that were explicitly set.
@hramezani
Copy link
Member

Thanks @kschwab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Question] Is it still possible to pass None through environment variables?
2 participants