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)

Combining Conditionals

Situation

In the following sections of this chapter, we are going to stick with the same example as the code snippet in the previous section. We'll improve it one step at a time.

Often, this is how you will approach refactoring: starting with the simplest refactoring. As your code becomes more complex or requires more TLC, then you can bring out the big guns.

Our scenario is a web application where we need to check some user permissions around editing a resource.

The Code

if(user.role === "admin" 
    && user.active 
    && user.permissions.some(p => p === "edit")) {
    
    // Do stuff.
}

How can we make this more readable, understandable, less prone to bugs, and easier to maintain?

One of the quick wins you can get with these kinds of verbose conditionals is to start by moving each one into its own variable.

Let's start with this:

const isAdmin: boolean = user.role === "admin...