Merged
Conversation
cdimascio
approved these changes
Mar 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When reading the README, I appreciated the simple and to-the-point documentation of how to get a dotenv value:
However the full path of the import isn't anywhere in the readme (I found it in the example code). I figured other people might be looking for that in the readme, so I just added that line to the above example:
I know some IDEs can import symbols like
Dotenvautomatically, and I'm also aware that those lines won't run directly since the import goes outside the class and theDotenv.load()would go inside some sort of main method, so I'm open to adding a...or otherwise restructuring that code snippet. What do you all think?