-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Apply test review changes #801
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
Conversation
tgolen
left a comment
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.
Great, thanks! Those descriptions on the tests really help. We still have an unresolved discussion about the config files, so I'll leave this open for a bit longer depending on how that conversation is resolved.
| const path = require('path'); | ||
| const dotenv = require('dotenv'); | ||
|
|
||
| const env = dotenv.config({path: path.resolve('./.env.example')}).parsed; |
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.
Wasn't exactly sure what .env file would be best, but I thought this one fit the best.. Let me know if you disagree @tgolen
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.
Oh, I actually hadn't considered the .env.example file. I was thinking maybe we would need a .env.testing file, but I think using the example file is brilliant 👍
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, I think using path can be overkill sometimes. I'm pretty sure this could be path: './.env.example'. I'm sure this was just from copy/pasting what we have elsewhere, but I would also say the same thing about wherever you copied it from.
| const path = require('path'); | ||
| const dotenv = require('dotenv'); | ||
|
|
||
| const env = dotenv.config({path: path.resolve('./.env.example')}).parsed; |
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, I think using path can be overkill sometimes. I'm pretty sure this could be path: './.env.example'. I'm sure this was just from copy/pasting what we have elsewhere, but I would also say the same thing about wherever you copied it from.
Pls review - @tgolen
Applies feedback from here: #415 (review) (sorry it's a bit late!)
Fixed Issues
Fixes N/A
Tests
Verify GitHub actions passes ✅