Enum vs union literal type trade-offs in Typescript - When to Use Which

The Big Idea

Discover how a small change in how you define options can save you hours of debugging!

The Scenario

Imagine you have a list of fixed options, like colors or directions, and you write separate checks everywhere in your code to handle each option manually.

The Problem

This manual checking is slow to write, easy to forget or mistype options, and hard to update when you add or remove choices. Bugs sneak in because the compiler can't help you catch mistakes.

The Solution

Using enums or union literal types lets TypeScript help you manage these fixed sets of options safely and clearly. They catch errors early and make your code easier to read and maintain.

Before vs After

✗ Before

function move(direction: string) {
  if (direction === 'up') { /*...*/ }
  else if (direction === 'down') { /*...*/ }
  // many more checks
}

✓ After

type Direction = 'up' | 'down' | 'left' | 'right';
function move(direction: Direction) { /*...*/ }

What It Enables

You can write safer, clearer code that the computer helps you check, reducing bugs and making changes easier.

Real Life Example

When building a menu with fixed options, using enums or union types ensures you never miss an option or mistype a value, keeping your app stable and predictable.

Key Takeaways

Manual checks for fixed options are error-prone and hard to maintain.

Enums and union literal types let TypeScript enforce valid values.

This leads to safer, cleaner, and easier-to-update code.

Practice

1. Which statement best describes a key difference between TypeScript enums and union literal types?

easy

A. Enums create runtime objects, while union literal types only exist at compile time.

B. Union literal types generate JavaScript code, enums do not.

C. Enums cannot restrict values, union literal types can.

D. Union literal types allow dynamic value assignment, enums do not.

Solution

1. Step 1: Understand enums and union literal types

   Enums create named objects that exist in the generated JavaScript code at runtime. Union literal types only exist during TypeScript's type checking and do not produce runtime code.

2. Step 2: Compare runtime presence

   Since union literal types are erased after compilation, they cannot be used as runtime objects, unlike enums.

3. Final Answer:

   Enums create runtime objects, while union literal types only exist at compile time. -> Option A

4. Quick Check:

   Runtime object presence = A [OK]

Hint: Enums exist at runtime; union types do not [OK]

Common Mistakes:

• Thinking union types generate runtime code
• Believing enums cannot restrict values
• Confusing dynamic assignment capabilities

2. Which of the following is the correct syntax to define a union literal type for colors 'red', 'green', and 'blue' in TypeScript?

easy

A. enum Colors { 'red', 'green', 'blue' }

B. type Colors = 'red' | 'green' | 'blue';

C. type Colors = ['red', 'green', 'blue'];

D. enum Colors = 'red' | 'green' | 'blue';

Solution

1. Step 1: Identify union literal type syntax

   Union literal types use the syntax: type Name = 'value1' | 'value2' | 'value3';

2. Step 2: Check options for correct syntax

   type Colors = 'red' | 'green' | 'blue'; correctly uses the union literal type syntax. Options B and D misuse enum syntax, and C defines a tuple type, not a union.

3. Final Answer:

   type Colors = 'red' | 'green' | 'blue'; -> Option B

4. Quick Check:

   Union literal type syntax = A [OK]

Hint: Union types use | between quoted literals [OK]

Common Mistakes:

• Using enum syntax for union types
• Using array syntax instead of union
• Assigning enum with = and union syntax mixed

3. Given the enum and union type below, what will be the output of the console.log statements?

enum StatusEnum { Active = 'active', Inactive = 'inactive' }
type StatusUnion = 'active' | 'inactive';

const enumValue = StatusEnum.Active;
const unionValue: StatusUnion = 'active';

console.log(enumValue === 'active');
console.log(unionValue === 'active');

medium

A. false false

B. true false

C. false true

D. true true

Solution

1. Step 1: Understand enum and union values

   StatusEnum.Active is assigned the string 'active'. The unionValue is also the string 'active'.

2. Step 2: Evaluate the console.log comparisons

   Both enumValue === 'active' and unionValue === 'active' compare string 'active' to 'active', so both are true.

3. Final Answer:

   true true -> Option D

4. Quick Check:

   String equality for enum and union = D [OK]

Hint: Enum string values equal union strings if assigned same literal [OK]

Common Mistakes:

• Assuming enum values are numbers by default
• Thinking enumValue is an object, not a string
• Confusing enum and union value types

4. Identify the error in the following TypeScript code using enums and union types:

enum Direction {
  Up = 'UP',
  Down = 'DOWN'
}

type DirectionUnion = 'UP' | 'DOWN';

function move(dir: DirectionUnion) {
  console.log(dir);
}

move(Direction.Up);
move('LEFT');

medium

A. Calling move with Direction.Up causes a type error.

B. Enum Direction is missing a 'LEFT' value causing an error.

C. Calling move with 'LEFT' causes a type error.

D. Function move should accept enum Direction, not union type.

Solution

1. Step 1: Check function parameter type

   Function move expects a parameter of type DirectionUnion, which allows only 'UP' or 'DOWN'.

2. Step 2: Analyze function calls

   Calling move(Direction.Up) passes 'UP', which is valid. Calling move('LEFT') passes a string not in the union, causing a type error.

3. Final Answer:

   Calling move with 'LEFT' causes a type error. -> Option C

4. Quick Check:

   Invalid union argument = B [OK]

Hint: Union types restrict allowed strings strictly [OK]

Common Mistakes:

• Assuming enum values are incompatible with union types
• Thinking missing enum values cause errors
• Believing function parameter types are flexible

5. You want to create a set of fixed string values representing user roles that can be checked at runtime and also provide type safety. Which approach is best and why?

// Option 1
enum UserRoleEnum { Admin = 'admin', User = 'user', Guest = 'guest' }

// Option 2
type UserRoleUnion = 'admin' | 'user' | 'guest';

hard

A. Use UserRoleEnum because it creates a runtime object for checks and type safety.

B. Use UserRoleUnion because it generates runtime code and is simpler.

C. Use UserRoleUnion because enums cannot restrict string values.

D. Use UserRoleEnum because union types cannot be used in type annotations.

Solution

1. Step 1: Understand runtime and type safety needs

   To check values at runtime, you need an actual JavaScript object. Enums generate this object. Union types only exist at compile time and do not generate code.

2. Step 2: Compare options for runtime checks and type safety

   UserRoleEnum provides both runtime presence and type safety. UserRoleUnion provides only type safety but no runtime object for checks.

3. Final Answer:

   Use UserRoleEnum because it creates a runtime object for checks and type safety. -> Option A

4. Quick Check:

   Runtime object + type safety = C [OK]

Hint: Enums create runtime objects; unions only type safety [OK]

Common Mistakes:

• Thinking union types generate runtime code
• Believing enums cannot restrict string values
• Assuming union types can be used for runtime checks