Why typed functions matter in Typescript - The Real Reasons

The Big Idea

What if your code could warn you about mistakes before you even run it?

The Scenario

Imagine you are writing a program where you have to pass many values between different parts of your code, but you have no clear idea what type of data each part expects. You might accidentally pass a number where a word is needed, or forget what kind of value a function should return.

The Problem

Without typed functions, you spend a lot of time guessing and testing what kind of data is allowed. This leads to bugs that are hard to find because errors only show up when the program runs, not when you write it. It's like trying to fit puzzle pieces without knowing their shapes.

The Solution

Typed functions tell you exactly what kind of data to give and what to expect back. This helps catch mistakes early, while you write code, making your programs safer and easier to understand. It's like having a clear instruction manual for every function.

Before vs After

✗ Before

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

✓ After

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

What It Enables

Typed functions make your code more reliable and easier to maintain by preventing many common mistakes before they happen.

Real Life Example

Think of a calculator app: typed functions ensure you only add numbers, not words, so the app won't crash or give wrong answers.

Key Takeaways

Typed functions clearly define what inputs and outputs are expected.

They catch errors early, saving time and frustration.

They make code easier to read and maintain for everyone.

Practice

1. Why is it important to specify types for function parameters and return values in TypeScript?

easy

A. It helps catch errors early by ensuring correct input and output types.

B. It makes the code run faster at runtime.

C. It allows functions to run without any input.

D. It automatically fixes bugs in the code.

Solution

1. Step 1: Understand the role of typed functions

   Typed functions define what types of inputs they accept and what type they return, helping the developer know how to use them correctly.

2. Step 2: Recognize the benefit of early error detection

   By specifying types, TypeScript can catch mistakes before running the code, preventing bugs caused by wrong data types.

3. Final Answer:

   It helps catch errors early by ensuring correct input and output types. -> Option A

4. Quick Check:

   Typed functions = early error detection [OK]

Hint: Typed functions catch type mistakes before running code [OK]

Common Mistakes:

• Thinking types speed up runtime
• Believing typed functions fix bugs automatically
• Assuming functions don't need inputs

2. Which of the following is the correct way to type a function in TypeScript that takes a number and returns a string?

easy

A. function convert(num: number) { return num.toString(); }

B. function convert(num: number): string { return num.toString(); }

C. function convert(num: string): number { return num.length; }

D. function convert(num): string { return num.toString(); }

Solution

1. Step 1: Check parameter and return types

   The function should accept a number parameter and return a string, so the parameter must be typed as number and the return type as string.

2. Step 2: Identify the correct syntax

   function convert(num: number): string { return num.toString(); } correctly types the parameter as number and the return type as string. function convert(num): string { return num.toString(); } misses parameter type, C swaps types, and A misses return type.

3. Final Answer:

   function convert(num: number): string { return num.toString(); } -> Option B

4. Quick Check:

   Parameter: number, Return: string = function convert(num: number): string { return num.toString(); } [OK]

Hint: Parameter and return types must match function purpose [OK]

Common Mistakes:

• Omitting parameter types
• Swapping parameter and return types
• Not specifying return type

3. What will be the output of this TypeScript code?

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

const result = add(5, 10);
console.log(result);

medium

A. 15

B. 510

C. undefined

D. Error: Type mismatch

Solution

1. Step 1: Analyze function parameters and return

   The function add takes two numbers and returns their sum as a number.

2. Step 2: Calculate the result of add(5, 10)

   Adding 5 and 10 gives 15, so result is 15 and console.log prints 15.

3. Final Answer:

   15 -> Option A

4. Quick Check:

   5 + 10 = 15 [OK]

Hint: Add numbers to get sum, not string concat [OK]

Common Mistakes:

• Thinking numbers concatenate as strings
• Expecting undefined return
• Assuming type error without mismatch

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

function greet(name: string): string {
  return 'Hello, ' + name;
}

greet(42);

medium

A. Remove the return type to fix the error.

B. Change function parameter to number: greet(name: number).

C. No error, code runs fine.

D. Change greet(42) to greet('42') to match string parameter.

Solution

1. Step 1: Check function parameter type

   The function expects a string parameter named name.

2. Step 2: Identify the call with wrong argument type

   The call greet(42) passes a number, which conflicts with the string type.

3. Step 3: Fix the call to match expected type

   Changing greet(42) to greet('42') passes a string, fixing the type mismatch.

4. Final Answer:

   Change greet(42) to greet('42') to match string parameter. -> Option D

5. Quick Check:

   Parameter type mismatch fixed by passing string [OK]

Hint: Match argument types to parameter types exactly [OK]

Common Mistakes:

• Ignoring type mismatch errors
• Removing return type instead of fixing input
• Changing parameter type without reason

5. You want a function that accepts either a string or number and returns a string describing the input type. Which typed function is correct?

hard

A. function describe(input: any): string {
return `Input: ${input}`;
}

B. function describe(input: string): string {
return `String: ${input}`;
}

C. function describe(input: string | number): string {
if (typeof input === 'string') return `String: ${input}`;
else return `Number: ${input}`;
}

D. function describe(input: number): string {
return `Number: ${input}`;
}

Solution

1. Step 1: Understand the input types needed

   The function must accept either string or number, so union type string | number is required.

2. Step 2: Check function logic and typing

   function describe(input: string | number): string { if (typeof input === 'string') return `String: ${input}`; else return `Number: ${input}`; } uses union type and checks input type to return correct description. Options C and D accept only one type, A uses any which loses type safety.

3. Final Answer:

   function describe(input: string | number): string { if (typeof input === 'string') return `String: ${input}`; else return `Number: ${input}`; } -> Option C

4. Quick Check:

   Union type with type check = function describe(input: string | number): string { if (typeof input === 'string') return `String: ${input}`; else return `Number: ${input}`; } [OK]

Hint: Use union types and type checks for multiple input types [OK]

Common Mistakes:

• Using any type losing safety
• Accepting only one type instead of both
• Not checking input type before returning