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)

Being Strategic

We're going to continue working with the code we refactored in the previous sections.

By extracting more specialized and targeted methods, we were able to abstract the details down to lower levels and label our logic.

Another cause of long methods that I've seen is when you get sections of code with lengthy logic inside conditionals.

Let's take this one in particular (which has some simulated logic):

const status: OrderStatus = order.getStatus();
if (status == OrderStatus.Pending) { 
 // Lots of logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
} else if (status == OrderStatus.Shipped) {
 // Lots of logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
} else if (status == OrderStatus.Cancelled) {
 // Lots of logic.
 // Lots more logic.
 // Lots more logic.
 // Lots more logic.
 ...