Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • React Design Patterns and Best Practices
  • Toc
  • feedback
React Design Patterns and Best Practices

React Design Patterns and Best Practices

By : Michele Bertoli
4 (8)
close
React Design Patterns and Best Practices

React Design Patterns and Best Practices

4 (8)
By: Michele Bertoli

Overview of this book

Taking a complete journey through the most valuable design patterns in React, this book demonstrates how to apply design patterns and best practices in real-life situations, whether that’s for new or already existing projects. It will help you to make your applications more flexible, perform better, and easier to maintain – giving your workflow a huge boost when it comes to speed without reducing quality. We’ll begin by understanding the internals of React before gradually moving on to writing clean and maintainable code. We’ll build components that are reusable across the application, structure applications, and create forms that actually work. Then we’ll style React components and optimize them to make applications faster and more responsive. Finally, we’ll write tests effectively and you’ll learn how to contribute to React and its ecosystem. By the end of the book, you’ll be saved from a lot of trial and error and developmental headaches, and you will be on the road to becoming a React expert.
Table of Contents (13 chapters)
close

Error handling with React

Even if we write excellent code and we cover all the code with tests, errors will still happen. The different browsers and environments, and real user data, are all variables that we cannot control and sometimes our code will fail. As developers, that is something we must accept.

The best thing we can do when problems happen in our applications is:

  • Notify the users and help them understand what happened and what they should do
  • Collect all useful information about the error and the state of the application in order to reproduce it and fix bugs quickly

The way React handle errors is slightly counter-intuitive in the beginning.

Suppose you have the following components:

const Nice => <div>Nice</div> 

And:

const Evil => ( 
  <div> 
    Evil 
    {this.does.not.exist} 
  </div> 
) 

Rendering the following App into the DOM, we would expect different things to happen:

const App = () => ( 
  <div> 
    <Nice /> 
    <Evil /> ...
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete