Often, applications require variables and functions that have multiple types of input or output. TypeScript has a special Union Type for such use cases, called Discriminated Unions.

Discriminated Unions in TypeScript are formed from two or more other types. A variable of discriminated union can be one of the types from the union.

Here's a simple example where a variable can hold either a number or a string:

typescript
1let id: number | string;
2id = 100; // This code is correct
3id = "200"; // This code is correct
4
5// TypeScript Error: Type 'boolean' is not assignable to type 'string | number'.
6id = false;

Unions are also useful when combining string literals. A literal in TypeScript is a special type for constant string, for example:

typescript
1let text: "TypeScript" = "TypeScript";
2text = "TypeScript"; // This code compiles
3
4// TypeScript Error: Type '"JavaScript"' is not assignable to type '"TypeScript"'.
5text = "JavaScript";

By combining literals into unions you can express that a variable can only accept a certain set of values:

typescript
1function print(value: string, align: "left" | "right" | "center") {
2    // ...
3}
4
5print("TypeScript types", "left");
6
7// TypeScript Error: "align" parameter should be one of: "left" | "right" | "center"
8print("TypeScript types", "middle");

When using discriminated unions, TypeScript will only allow to access properties or methods that are common to all types in the union. To use type-specific properties or methods, you need to use type guards for built-in types:

typescript
1function getLength(obj: string | string[]) {
2    if (typeof obj === "string") {
3        return obj.length; // Return length of a string
4    }
5
6    return obj.length; // Return legnth of string array
7}

Discriminated Unions can combine object types too. Let's explore an example of geometrics shapes, that have common and different properties:

typescript
1type Circle = {
2    type: "circle";
3    radius: number;
4};
5
6type Square = {
7    type: "square";
8    size: number;
9};

Let's create a function that calculates a square for each shape:

typescript
1function getSquare(shape: Circle | Square) {
2    if (shape.type === "circle") {
3        return Math.PI * shape.radius * shape.radius;
4    }
5
6    if (shape.type === "square") {
7        return shape.size * shape.size;
8    }
9}
10
11const circle: Circle = {
12    type: "circle",
13    radius: 10
14};
15
16const square: Square = {
17    type: "square",
18    size: 5
19};
20
21console.log("Circle square: ", getSquare(circle));
22console.log("Circle square: ", getSquare(square));

Here a getSquare function accepts a shape parameter that can be one of 2 types: Circle or Square. When working with custom types you can use a property that will allow to distinguish types from each other. In our example it's a type property. Type guards here are straightforward:

typescript
1function getSquare(shape: Circle | Square) {
2    if (shape.type === "circle") {
3        return Math.PI * shape.radius * shape.radius;
4    }
5
6    if (shape.type === "square") {
7        return shape.square;
8    }
9    
10    return 0;
11}

TypeScript is smart enough to know that we are working with Circle or Square type.

Another example where discriminated unions are useful - is a function return type. Let's explore an example of placing an order for a product by its ID and desired quantity. The return type of this function will be a discriminated union representing three possible states:

• order successfully created
• product not found
• not enough product quantity in the warehouse

The naive approach is to declare a big object with properties that cover all three cases. But such implementation is cumbersome.

Discriminated unions offer a more elegant approach:

typescript
1type OrderResponse = OrderCreated | ProductNotFound | NoProductQuantity;
2
3type OrderCreated = {
4    type: "order-created";
5    orderId: string;
6    message: string;
7};
8
9type ProductNotFound = {
10    type: "product-not-found";
11    message: string;
12};
13
14type NoProductQuantity = {
15    type: "no-product-quantity";
16    message: string;
17};

Now we can use this union type as a function's return type. We are getting products from a database or an external API, but for simplicity we will mock the data:

typescript
1function orderProduct(productId: string, quantity: number): OrderResponse {
2    const productsDatabase = {
3        "Mobile Phone": { stock: 10 },
4        "Smart TV": { stock: 0 },
5    };
6
7    const product = productsDatabase[productId];
8    
9    if (!product) {
10        return {
11            type: "product-not-found",
12            message: "Product not found"
13        };
14    }
15    
16    if (quantity > product.stock) {
17        return {
18            type: "no-product-quantity",
19            message: "Insufficient product quantity"
20        };
21    }
22    
23    return {
24        type: "order-created",
25        orderId: `order-${new Date().getTime()}`,
26        message: "Order has been successfully created"
27    };
28}

In this function we are returning 3 types of responses: "order-created", "product-not-found", "no-product-quantity". To order a product let's call the method:

typescript
1const orderResult = orderProduct("Mobile Phone", 1);
2
3switch (orderResult.type) {
4    case "order-created":
5        console.log(`Success: ${orderResult.message} (Order ID: ${orderResult.orderId})`);
6        break;
7    case "product-not-found":
8        console.log(`Error: ${orderResult.message}`);
9        break;
10    case "no-product-quantity":
11        console.log(`Error: ${orderResult.message}`);
12        break;
13}

As you can see discriminated unions make code more readable and maintainable in such use cases.

Discriminated unions in TypeScript offer a robust way to manage different data types under a united type. They enhance type safety, improve code clarity, and ensure that all possible cases are handled, reducing runtime errors. Using discriminated unions as function input and output types will significantly improve the quality and maintainability of your TypeScript applications.

Hope you find this newsletter useful. See you next time.