Why type annotations are needed in Typescript - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this TypeScript code with type annotations?

Look at this TypeScript code. What will it print when run?

Typescript

function greet(name: string): string {
  return `Hello, ${name}!`;
}

console.log(greet("Alice"));

A SyntaxError

B Hello, Alice!

C TypeError at runtime

D Hello, undefined!

💡 Hint

Think about what the function returns and the argument passed.

The function greet takes a string and returns a greeting string. Passing "Alice" returns "Hello, Alice!".

🧠 Conceptual

intermediate

Why do we use type annotations in TypeScript?

Which of these is the main reason to use type annotations in TypeScript?

A To reduce the file size of the code

B To make the code run faster

C To catch errors before running the code

D To make the code look prettier

💡 Hint

Think about when errors are found in TypeScript compared to JavaScript.

Type annotations help the TypeScript compiler find mistakes before the program runs, making code safer.

❓ Predict Output

advanced

What error does this TypeScript code raise without type annotations?

Consider this TypeScript code without type annotations. What error will it cause?

Typescript

function add(a, b) {
  return a + b;
}

console.log(add(5, "10"));

A 510

B 15

C TypeError at runtime

D Compilation error due to missing types

💡 Hint

Think about what happens when you add a number and a string in JavaScript.

Without type annotations, add(5, "10") concatenates as string, resulting in "510".

🔧 Debug

advanced

Identify the error caused by missing type annotations

What error will this TypeScript code produce when compiled?

Typescript

function multiply(a: number, b: number) {
  return a * b;
}

console.log(multiply(4, "3"));

A Compilation error: Argument of type 'string' is not assignable to parameter of type 'number'.

B Runtime error: Cannot multiply number and string

C Output: 12

D No error, outputs '43'

💡 Hint

Check the types of arguments passed to the function.

TypeScript catches the wrong argument type at compile time because of type annotations.

🚀 Application

expert

How do type annotations improve code maintenance?

Choose the best explanation of how type annotations help maintain large TypeScript projects.

A They allow the program to run without any testing.

B They automatically fix bugs in the code without developer input.

C They speed up the program execution by optimizing machine code.

D They make it easier to understand what data types functions expect and return, reducing bugs when changing code.

💡 Hint

Think about how clear type information helps developers work on code safely.

Type annotations serve as clear documentation and help tools catch mistakes early, making code easier to maintain.

Practice

1. Why do we use type annotations in TypeScript?
let age: number = 25;

easy

A. To tell the computer what kind of data to expect

B. To make the program run faster

C. To hide the data from other parts of the program

D. To automatically fix errors in the code

Solution

1. Step 1: Understand the purpose of type annotations

   Type annotations specify the kind of data a variable should hold, like number or string.

2. Step 2: Identify the benefit in the example

   In let age: number = 25;, the annotation number tells the computer to expect a number value.

3. Final Answer:

   To tell the computer what kind of data to expect -> Option A

4. Quick Check:

   Type annotations = tell data type [OK]

Hint: Type annotations describe data type before running code [OK]

Common Mistakes:

• Thinking type annotations speed up program execution
• Believing type annotations hide data
• Assuming type annotations fix errors automatically

2. Which of the following is the correct way to add a type annotation for a string variable in TypeScript?

easy

A. let name = string 'Alice';

B. let name == 'Alice': string;

C. let name: 'Alice' = string;

D. let name: string = 'Alice';

Solution

1. Step 1: Recall TypeScript syntax for type annotations

   The correct syntax is let variableName: type = value;.

2. Step 2: Match syntax with options

   let name: string = 'Alice'; matches this syntax: let name: string = 'Alice'; is correct.

3. Final Answer:

   let name: string = 'Alice'; -> Option D

4. Quick Check:

   Correct syntax = let name: string = 'Alice'; [OK]

Hint: Use colon after variable name for type [OK]

Common Mistakes:

• Using '=' instead of ':' for type annotation
• Placing type after value
• Using double equals '==' for assignment

3. What will happen when you run this TypeScript code?

let count: number = 10;
count = 'ten';

medium

A. The code runs but count remains 10

B. The code runs and count becomes 'ten'

C. A compile-time error occurs because 'ten' is not a number

D. A runtime error occurs when assigning 'ten'

Solution

1. Step 1: Check the declared type of count

   Variable count is declared as number.

2. Step 2: Analyze the assignment of a string to a number

   Assigning 'ten' (a string) to count violates the type annotation.

3. Step 3: Understand TypeScript behavior

   TypeScript will show a compile-time error before running the code.

4. Final Answer:

   A compile-time error occurs because 'ten' is not a number -> Option C

5. Quick Check:

   Type mismatch = compile-time error [OK]

Hint: Assign values matching declared type to avoid errors [OK]

Common Mistakes:

• Thinking TypeScript allows wrong type assignments at runtime
• Confusing compile-time and runtime errors
• Assuming variable value stays unchanged silently

4. Identify the error in this TypeScript code and choose the fix:

function greet(name) {
  return 'Hello, ' + name.toUpperCase();
}
greet(123);

medium

A. Call greet with a string instead of a number

B. Add type annotation: name: string in function parameter

C. Remove the function parameter

D. Change toUpperCase() to toString()

Solution

1. Step 1: Understand the error cause

   The function expects a string to call toUpperCase(), but 123 is a number.

2. Step 2: Fix by adding type annotation

   Adding name: string tells TypeScript to expect a string and catch wrong calls like greet(123).

3. Final Answer:

   Add type annotation: name: string in function parameter -> Option B

4. Quick Check:

   Type annotation prevents wrong argument types [OK]

Hint: Add parameter types to catch wrong argument types early [OK]

Common Mistakes:

• Ignoring type annotations and relying on runtime errors
• Changing method instead of fixing parameter type
• Removing parameters instead of typing them

5. You have this TypeScript function:

function calculateArea(width, height) {
  return width * height;
}

How can adding type annotations improve this function?

hard

A. By ensuring both width and height are numbers to avoid wrong calculations

B. By making the function run faster

C. By allowing width and height to be any type

D. By automatically converting strings to numbers

Solution

1. Step 1: Identify the problem without type annotations

   Without types, width and height can be any type, causing wrong results if strings or other types are passed.

2. Step 2: Add type annotations to improve safety

   Adding width: number and height: number ensures only numbers are accepted, preventing errors.

3. Final Answer:

   By ensuring both width and height are numbers to avoid wrong calculations -> Option A

4. Quick Check:

   Type annotations improve input safety [OK]

Hint: Type inputs to avoid wrong data causing bugs [OK]

Common Mistakes:

• Thinking type annotations speed up execution
• Assuming type annotations convert data types automatically
• Allowing any type defeats purpose of annotations