-
Notifications
You must be signed in to change notification settings - Fork 975
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
Explain behavior of config.get
#6611
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
made some small typos and looks good! thanks @dbeatty10 !
@mirnawong1 thank you so much for fixing this up 🧠 ! For such a small PR, I sure had a high density of typos 😅 -- thanks for having my back and getting it on track! 🛤️ |
resolves #3969
What are you changing in this pull request and why?
Details in #3969
TLDR
The key insight is that many people expect
config.get("foo", default="bar")
to act likecoalesce
in SQL, but it does not.There are cases where users will want to use an alternative value whenever
config.get("something")
isNone
(similar tocoalesce
in SQL). This PR documents how to do that.Checklist
🚀 Deployment available! Here are the direct links to the updated files: