Refactoring to clean code
About the Book
We all know the most significant coding efforts in any real-life project are not about writing new code but maintaining the existing one. And a considerable part of our time is spent trying to understand the legacy code.
In this book, I'm trying to put together common patterns I found in many React projects I've worked on: what worked well and what didn't, the symptoms of issues and how to get rid of them with proven techniques.
I hope it can help you cope with your project's challenges, save time writing new features, and improve the code base with each commit.
Table of Contents
- Do we need another book on the topic?
- How the book is structured
Chapter 0 - React Clean Code
- What is clean code?
- Clean code
- Clean up techniques
Chapter 0.5 - How to organise your React application
- Front-end applications are complex
- How to split your projects
Chapter 1 - Brief of Test-Driven Development
- Introduction to the Test-Driven Development process
- Typical workflow of TDD
- Write our first test
Chapter 2 - Todo Application - Basic Features
- Get started with Todo application
- Renders single item
- Renders multiple items
- Data structure of an item
- Add a new item to the todo list
Chapter 3 - Refactor - Separation of Concerns
- Separation of concerns
- Extract a new component
- Using the new component in Todo application
Chapter 4 - Adding New Feature - Mark Item As Done
- Adding a new test
- Type changes
- Handle click event on item
- Filter out completed items
Chapter 5 - Refactor - Split Logic Into Custom Hook
- Another round of refactoring
- Extract the TodoList component
- Custom hook for business logic
- What we have learnt
Chapter 6 - Composition Foundation
- children / slots pattern
- Passing multiple nodes
Chapter 7 - Refactor - AddressContainer
- Using render prop to decoupling
- More fancy rendering
Chapter 8 - Composition Example 1 - The Avatar component
- The tooltip prop
- Break the dependency chain
Composition Example 2 - InlineEdit
- The InlineEdit component
- The validate prop
- Refactoring Option 1
- Refactoring Option 2
The refactor of StackView Component
- The StackView component
- Optional header and footer component
- New request - the user profile
- Quiz - what’s the problem here?
- Break it down and reassemble it back
Business logic leaking
- The do-all-things view
- The business logic leakage
Fix the Leakage - Data Modelling
- A address searching box
- Current implementation
- Data modelling
Project simulation - Direct To Boot
- First test
- The component
Feature: Notify the store
- Custome hook
- Notified message
- Look at the code
10 Refactorings to Boost your Clean Code Efficiency
- The most common 10 refactorings
- Code smells
- Common Refactorings
- The Problem - ROT13
- The implementation
The Leanpub 60-day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $12 million USDwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them