Skip to content
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

WIP: Add the guide level document about null vs undefined #741

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tetsuharuohzeki
Copy link
Contributor

This attempt to fix #732.


As a personal duty of maintaining a library like providing a toolkit utilities to handle nullabltily for JavaScript, I challenge to answer a long standing question - which should we use null - by this document.

I was asked many times from my colleagues that what should we use null or undefined when we design an interface. In almost case, my answer is that "null would be nice if you'd like to express to return a none value. It has a strong intent" with some (often a bunch of) reasons. I belive my answer would be a right decision but that does not stands by any investigations for that history and current situations of the ecosystem. So this guide presents some helps to you when you're worry about which you should use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write up a guide about null vs undefined
1 participant