-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add support for crate specific .env files #270
Add support for crate specific .env files #270
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.
Looks good to me minus a couple nits.
8dfd088
to
d52576c
Compare
d52576c
to
f3265c6
Compare
Changes made, rebased + pushed 😃 |
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.
Sorry, one last nit and then it's good to go. It's not super important, just sort of a "best practices" thing.
This change will attempt to load an .env file from CARGO_MANIFEST_DIR, if it exists. For backwards compatibility, if the .env file does not exist, we will fall back to default dotenv behaviour. Resolves launchbadge#267
f3265c6
to
f9a7b66
Compare
Thanks for the contribution here 👍 |
This change will attempt to load an .env file from CARGO_MANIFEST_DIR, if it exists.
For backwards compatibility, if the .env file does not exist, we will fall back to default dotenv behaviour.
Resolves #267