Book Image

Refactoring TypeScript

By : James Hickey
Book Image

Refactoring TypeScript

By: James Hickey

Overview of this book

Refactoring improves your code without changing its behavior. With refactoring, the best approach is to apply small targeted changes to a codebase. Instead of doing a huge sweeping change to your code, refactoring is better as a long-term and continuous enterprise. Refactoring TypeScript explains how to spot bugs and remove them from your code. You’ll start by seeing how wordy conditionals, methods, and null checks make code unhealthy and unstable. Whether it is identifying messy nested conditionals or removing unnecessary methods, this book will show various techniques to avoid these pitfalls and write code that is easier to understand, maintain, and test. By the end of the book, you’ll have learned some of the main causes of unhealthy code, tips to identify them and techniques to address them.
Table of Contents (11 chapters)

Value Objects

Scenario

We've been working on email logic for a Software-as-a-Service (SaaS) product. Lately, working with this part of the code base has caused inadvertent bugs to appear.

We've decided that now is a good time to reach in, clean it up, and improve its overall quality.

From a high-level perspective, our code is checking whether an email address is sent to a specific internal domain (such as internal-company.com). If the username (that is, the email address' local-part) is info, then we send the email to our internal customer support team. Otherwise, we just send it to the intended recipient.

Here's our code:

const domain: string = email.replace(/.*@/, "");
const userName = email.replace(domain, "");
const sendInternal: boolean = domain === "internal-company.com";
if(sendInternal) {
    if(userName === "info") {
        mailer.sendToCustomerServiceTeam(email, message);
    } else {
        mailer...