From ade7fbfa3b65b3f758a8a0e10e0b76066a5c93d7 Mon Sep 17 00:00:00 2001
From: roadmap bot <135830415+roadmap-bot@users.noreply.github.com>
Date: Tue, 13 Jun 2023 11:35:46 +0100
Subject: [PATCH] chore: add resource under
 typescript:typescript-types:type-assertions:as-type

---
 .../101-typescript-types/115-type-assertions/101-as-type.md     | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/data/roadmaps/typescript/content/101-typescript-types/115-type-assertions/101-as-type.md b/src/data/roadmaps/typescript/content/101-typescript-types/115-type-assertions/101-as-type.md
index 85c73824d..94d892f49 100644
--- a/src/data/roadmaps/typescript/content/101-typescript-types/115-type-assertions/101-as-type.md
+++ b/src/data/roadmaps/typescript/content/101-typescript-types/115-type-assertions/101-as-type.md
@@ -12,3 +12,5 @@ let str = num as string;
 ```
 
 It's important to note that type assertions do not change the runtime type of a value, and do not cause any type of conversion. They simply provide a way for the programmer to override the type inference performed by the compiler.
+
+- [Type assertions](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#type-assertions)
\ No newline at end of file