dotenv-safe instead of manual checking a hardcodet whitelist
@vpanjganj is already working on this.
Since Nov 22, 2018.
Assessment
This issue has not been assessed yet.
Description
Maybe its an idea to use dotenv-safe, with that you can define the needed env variables in the .env.example (the optional ones can be prefixed with # ).
- Dominant language
- JavaScript
- Stars
- 29.4k
- Forks
- 3.1k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from elsewhencode/project-guidelines
-
AQUAEDGE PROMOTIONS Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
elsewhencode/project-guidelines#176 · 1 comment ·
-
improvement
elsewhencode/project-guidelines#160 · 3 reactions · 1 assignee ·
-
improvement
elsewhencode/project-guidelines#140 · 1 assignee ·
-
improvement question
elsewhencode/project-guidelines#134 · 1 assignee ·
-
help wanted improvement
elsewhencode/project-guidelines#124 · 2 comments · 6 reactions · 1 assignee ·
All issues in elsewhencode/project-guidelines
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·