Book Image

React Design Patterns and Best Practices

By : Michele Bertoli
Book Image

React Design Patterns and Best Practices

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 (19 chapters)
React Design Patterns and Best Practices
About the Author
About the Reviewer
Customer Feedback

Contributing to React

One thing that people often want to do when they've used React for a while is to contribute to the library. React is open source which means that its source code is public and anyone who's signed the Contributor License Agreement (CLA) can help to fix bugs, write documentation, or even add new features.

You can read the full terms of the CLA at the following URL:

Suppose, for example, you were building an application with React and you found a bug, what should you do? The first and most important thing is to create a small reproducible example of the problem. To do that, there is a handy JSFiddle template provided by the React team:

This operation has two key benefits:

  • It helps you to be 100% confident that the bug is effectively a React bug and not just an issue with your application code

  • It helps the React team understand the problem quickly without having to delve into your application code, making...