Book Image

Redux Made Easy with Rematch

By : Sergio Moreno
Book Image

Redux Made Easy with Rematch

By: Sergio Moreno

Overview of this book

Rematch is Redux best practices without the boilerplate. This book is an easy-to-read guide for anyone who wants to get started with Redux, and for those who are already using it and want to improve their codebase. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will take you from the simplest through to the most complex layers of Rematch. You’ll learn how to migrate from Redux, and write plugins to set up a fully tested store by integrating it with vanilla JavaScript, React, and React Native. You'll then build a real-world application from scratch with the power of Rematch and its plugins. As you advance, you’ll see how plugins extend Rematch functionalities, understanding how they work and help to create a maintainable project. Finally, you'll analyze the future of Rematch and how the frontend ecosystem is becoming easier to use and maintain with alternatives to Redux. By the end of this book, you'll be able to have total control of the application state and use Rematch to manage its scalability with simplicity.
Table of Contents (18 chapters)
1
Section 1: Rematch Essentials
6
Section 2: Building Real-World Web Apps with Rematch
11
Section 3: Diving Deeper into Rematch

Creating the shop business logic

As we explained in Chapter 5, React with Rematch – The Best Couple – Part I, in the Preparing the environment section, we're using an interesting NPM module named json-server (https://github.com/typicode/json-server) that converts static JavaScript Object Notation (JSON) files to API endpoints ready to use. This module is really powerful for this book because it will allow us to call a fake API to access the data. A real API recovers the data from a database, but in our case, this data is just static. However, the way this data is accessed from our side, on the frontend, is the same as would be employed in a real API.

When we start our application with yarn dev, it automatically runs a server on http://localhost:3000 to see the refreshed changes of our frontend application, while also running a server on http://localhost:8000. If we access this URL, we should see something like this:

Figure 6.1 –...