Type alias vs inline types in Typescript - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a type alias for a user object.

Typescript

type User = [1];

Drag options to blanks, or click blank then click option'

A[string, number]

B{ name: string; age: number }

Cstring | number

Dboolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using array syntax instead of object syntax.

Using union types instead of object types.

The correct syntax for a type alias defining an object type uses curly braces with property names and types.

2fill in blank

medium

Complete the function parameter type using an inline type instead of a type alias.

Typescript

function greet(user: [1]) { console.log(`Hello, ${user.name}`); }

Drag options to blanks, or click blank then click option'

Anumber

BUser

Cstring

D{ name: string; age: number }

Attempts:

3 left

💡 Hint

Common Mistakes

Using a type alias name instead of inline type.

Using primitive types like string or number instead of object type.

Inline types are written directly in the parameter list using curly braces to describe the object shape.

3fill in blank

hard

Fix the error in the type alias declaration for a product with id and name.

Typescript

type Product = [1];

Drag options to blanks, or click blank then click option'

A{ id: number; name: string }

B(id: number, name: string) => void

C[number, string]

Dnumber | string

Attempts:

3 left

💡 Hint

Common Mistakes

Using function type syntax instead of object type.

Using tuple or union types instead of object type.

The type alias for an object must use curly braces with property names and types, not function or tuple syntax.

4fill in blank

hard

Fill both blanks to create a type alias and use it in a function parameter.

Typescript

type [1] = { title: string; pages: number };
function printBook(book: [2]) { console.log(book.title); }

Drag options to blanks, or click blank then click option'

ABook

BArticle

DMagazine

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the type alias and parameter type.

Using inline type in one place and alias in another.

The type alias name must be the same in both declaration and usage to match the type.

5fill in blank

hard

Fill all three blanks to define a type alias, use it inline, and declare a variable with that type.

Typescript

type [1] = { x: number; y: number };
const point: [2] = { x: 10, y: 20 };
function logPoint(p: [3]) { console.log(`x: ${p.x}, y: ${p.y}`); }

Drag options to blanks, or click blank then click option'

APoint

DCoordinate

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for the type alias in different places.

Mixing inline types and type aliases inconsistently.

Using the same type alias name consistently for declaration, variable type, and function parameter ensures type safety and clarity.

Practice

1. What is the main advantage of using a type alias in TypeScript compared to inline types?

easy

A. It makes the code run faster at runtime.

B. It automatically checks for runtime errors.

C. It allows reusing the same type definition multiple times with a clear name.

D. It removes the need to write types altogether.

Solution

1. Step 1: Understand what a type alias does

   A type alias gives a name to a type, so you can use it repeatedly without rewriting the full type.

2. Step 2: Compare with inline types

   Inline types are written directly where needed and are not reusable by name, making code less clear if repeated.

3. Final Answer:

   It allows reusing the same type definition multiple times with a clear name. -> Option C

4. Quick Check:

   Type alias = reusable named type [OK]

Hint: Type alias = named reusable type, inline = one-time use [OK]

Common Mistakes:

• Thinking type aliases affect runtime speed
• Confusing type aliases with runtime error checking
• Believing type aliases remove the need for types

2. Which of the following is the correct syntax to define a type alias for an object with a name string and age number?

easy

A. type Person = { name: string; age: number };

B. alias Person = { name: string; age: number };

C. type Person := { name: string; age: number };

D. define Person = { name: string; age: number };

Solution

1. Step 1: Recall TypeScript type alias syntax

   The correct syntax uses the keyword type, followed by the alias name, an equals sign, and the type definition.

2. Step 2: Check each option

   Only type Person = { name: string; age: number }; matches the correct syntax exactly. Others use invalid keywords or symbols.

3. Final Answer:

   type Person = { name: string; age: number }; -> Option A

4. Quick Check:

   Correct alias syntax = type Name = Type [OK]

Hint: Type alias syntax always starts with 'type' keyword [OK]

Common Mistakes:

• Using 'alias' instead of 'type'
• Using ':=' instead of '='
• Using 'define' keyword which is invalid

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

type Point = { x: number; y: number };

const p1: Point = { x: 5, y: 10 };
const p2: { x: number; y: number } = { x: 5, y: 10 };

console.log(p1.x === p2.x && p1.y === p2.y);

medium

A. undefined

B. false

C. Type error at compile time

D. true

Solution

1. Step 1: Understand type alias and inline type usage

   Both p1 and p2 have the same shape: objects with x and y numbers.

2. Step 2: Compare the values

   Both objects have x: 5 and y: 10, so the comparison p1.x === p2.x && p1.y === p2.y is true.

3. Final Answer:

   true -> Option D

4. Quick Check:

   Same shape objects compare equal values = true [OK]

Hint: Type alias or inline same shape means same type [OK]

Common Mistakes:

• Thinking type alias creates different runtime objects
• Expecting compile error due to inline vs alias
• Confusing object reference equality with value equality

4. Identify the error in this TypeScript code snippet:

type User = { id: number; name: string };

const user: User = { id: 1, name: 'Alice', age: 30 };

medium

A. The property 'name' should be a number, not a string.

B. Extra property 'age' is not allowed in the object assigned to type User.

C. Type alias cannot be used for object types.

D. Missing semicolon after type alias definition.

Solution

1. Step 1: Check the type alias definition

   The type alias User expects an object with only id and name properties.

2. Step 2: Check the assigned object

   The object has an extra property age which is not defined in User, causing a TypeScript error.

3. Final Answer:

   Extra property 'age' is not allowed in the object assigned to type User. -> Option B

4. Quick Check:

   Extra properties not in type cause error [OK]

Hint: Object must match type exactly; no extra properties [OK]

Common Mistakes:

• Ignoring extra properties in object literals
• Thinking semicolon is mandatory after type alias
• Confusing property types in the alias

5. You want to define a reusable type for a product with id (number), name (string), and an optional description (string). Which approach is best and why?

Options:
A) Use a type alias for the product type and reuse it.
B) Use inline types everywhere the product is used.
C) Use a class instead of a type alias.
D) Use a union type of string and number for all properties.

hard

A. Use a type alias for the product type and reuse it.

B. Use inline types everywhere the product is used.

C. Use a class instead of a type alias.

D. Use a union type of string and number for all properties.

Solution

1. Step 1: Consider reusability and clarity

   A product type is used multiple times, so naming it with a type alias improves clarity and reuse.

2. Step 2: Evaluate other options

   Inline types cause repetition and clutter. Classes add runtime overhead and are not necessary here. Union types for all properties are incorrect and confusing.

3. Final Answer:

   Use a type alias for the product type and reuse it. -> Option A

4. Quick Check:

   Reusable complex types = type alias [OK]

Hint: Use type alias for reusable complex types [OK]

Common Mistakes:

• Using inline types repeatedly causing duplication
• Confusing classes with type aliases
• Misusing union types for unrelated properties