Skip to content
This repository was archived by the owner on Oct 12, 2022. It is now read-only.

Fix documentation on --strictNullChecks #1053

Merged
merged 2 commits into from
Jun 24, 2019
Merged

Fix documentation on --strictNullChecks #1053

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
98618ca
Fix documentation on --strictNullChecks
karlhorky Jun 24, 2019
fdd6ba4
Add undefined / void exception
karlhorky Jun 24, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pages/Basic Types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -204,7 +204,7 @@ let n: null = null;
By default `null` and `undefined` are subtypes of all other types.
That means you can assign `null` and `undefined` to something like `number`.

However, when using the `--strictNullChecks` flag, `null` and `undefined` are only assignable to `void` and their respective types.
However, when using the `--strictNullChecks` flag, `null` and `undefined` are only assignable to `any` and their respective types (the one exception being that `undefined` is also assignable to `void`).
This helps avoid *many* common errors.
In cases where you want to pass in either a `string` or `null` or `undefined`, you can use the union type `string | null | undefined`.
Once again, more on union types later on.
Expand Down