Skip to content

Utility Types.md: clarify NoInfer usage #3623

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.

Sign up for GitHub

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

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

Utility Types.md: clarify NoInfer usage #3623

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 2 additions & 0 deletions packages/documentation/copy/en/reference/Utility Types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -464,6 +464,8 @@ Released:
Blocks inferences to the contained type. Other than blocking inferences, `NoInfer<Type>` is
identical to `Type`.

For example, the `createStreetLight()` function below is called with a `colors` value of `["red", "yellow", "green"]`, making the `C` type parameter be a union of `"red" | "yellow" | "green"` (so `"blue"` would not be a valid default), but if `NoInfer<C>` was not used, the `defaultColor`'s type of `"blue"` would get added to the type parameter union, so the compiler would consider `"blue"` as a valid default even though it's not in the list of `colors`.

##### Example

```ts
Expand Down