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)

Identification

A Monster

I once worked on a project that had a particular function with ~ 5,000 lines of code in it.

Yes – one function with about 5,000 lines of code.

Welcome to the real world.

Inside this function was basically one massive switch statement with lots of nested if statements.

It was really hard to understand.

Code like this is really common, though. One day, a developer comes along and adds a couple more conditionals. Another day, someone adds a few more. Next thing you know, it's a huge mess of nested conditionals that no one understands anymore.

A Closer Look

These nested conditionals can look something like this:

let result: OrderResult = null;
if(!order.wasCancelled()) {
    if(order.isPaid()) {
        result = order.sendToShipping();
    } else {
        if(order.isFraudulent()) {
            result = order.sendToFraudDept();
        } else {
            result = order.tryAgainLater();
        }
    }
}
return result...