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)

Extracting Methods from Conditionals

Consider the code we had in the previous section:

const isAdmin: boolean = user.role === "admin";
const userIsActive: boolean = user.active;
const userCanEdit: boolean = user.permissions.some(p => p === "edit");
const activeAdminCanEdit: boolean = isAdmin && userIsActive && userCanEdit;
if(activeAdminCanEdit) {
    // Do stuff.
}

In some cases, the above code is fine.

In other cases, sometimes, you just get that feeling... something's not right.

What's Wrong Here?

Let's think through this code.

Is it possible that somewhere else in our application we will need to check whether:

  • A user is an admin?
  • A user is active?
  • A user can edit certain resources?

The answer is... probably... yes.

Right now, is that logic able to be accessed by other parts of your application?

Nope.

Oh, yeah. There's another thing. All of these conditionals are performed...