WIP: Add the guide level document about null
vs undefined
#741
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
orundefined
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.