Skip to content

Bring back the note about type safety of any from the old docs #3470

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
klesun-st wants to merge 1 commit into
base: v2
Choose a base branch
from
Open

Bring back the note about type safety of any from the old docs #3470

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
3 changes: 3 additions & 0 deletions packages/documentation/copy/en/handbook-v2/Everyday Types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,8 @@ const n: number = obj;

The `any` type is useful when you don't want to write out a long type just to convince TypeScript that a particular line of code is okay.

After all, remember that all the convenience of `any` comes at the cost of losing type safety. Type safety is one of the main motivations for using TypeScript and you should try to avoid using `any` when not necessary.

### `noImplicitAny`

When you don't specify a type, and TypeScript can't infer it from context, the compiler will typically default to `any`.
Expand Down Expand Up @@ -735,3 +737,4 @@ if (firstName === secondName) {
```

You can learn more about them in [Symbols reference page](/docs/handbook/symbols.html).