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)

One of These Things Is Not Like The Others

There's a programming principle we saw earlier in the book called the Single Responsibility Principle.

When looking at classes or methods that are doing too much, using the SRP as a guiding light can help us to make code that is easier to maintain, less coupled, and therefore leads to fewer bugs.

Let's look at a generic User class that might be similar to code that you've seen before:

class User {
    public firstName: string;
    public lastName: string;
    public id: number;
    public jwtToken: string;
    public homeAddress: string;
    public creditCardNo: string;
    public getFullName(): string {
        return this.firstName + " " + this.lastName;
    }
    public decodeJwtToken(): string {
        return decode(this.jwtToken);
    }
}

Look familiar?

Given the name of the class, we should start to be suspicious that it's too generic a class...

You Have Mail

You've been tasked...