Book Image

Redux Quick Start Guide

By : James Lee, Tao Wei, Suresh Kumar Mukhiya
Book Image

Redux Quick Start Guide

By: James Lee, Tao Wei, Suresh Kumar Mukhiya

Overview of this book

Starting with a detailed overview of Redux, we will follow the test-driven development (TDD) approach to develop single-page applications. We will set up JEST for testing and use JEST to test React, Redux, Redux-Sage, Reducers, and other components. We will then add important middleware and set up immutableJS in our application. We will use common data structures such as Map, List, Set, and OrderedList from the immutableJS framework. We will then add user interfaces using ReactJS, Redux-Form, and Ant Design. We will explore the use of react-router-dom and its functions. We will create a list of routes that we will need in order to create our application, and explore routing on the server site and create the required routes for our application. We will then debug our application and integrate Redux Dev tools. We will then set up our API server and create the API required for our application. We will dive into a modern approach to structuring our server site components in terms of Model, Controller, Helper functions, and utilities functions. We will explore the use of NodeJS with Express to build the REST API components. Finally, we will venture into the possibilities of extending the application for further research, including deployment and optimization.
Table of Contents (16 chapters)
Title Page
Copyright and Credits
Dedication
About Packt
Contributors
Preface
Index

Frequently asked questions


Let's look at a list of frequently asked questions related to Immutable.js, as follows:

  1. Do I need Immutable JS in my application?

If you are not sure what benefits Immutable JS can bring to your application, you should not use it. Just because a library is being used by enterprise applications does not mean that you have to use it. Before considering using it, you should understand it and feel a need for using it.

  1. Is there something wrong with mutating objects?

There is nothing wrong with mutation. Several developers in the community have discussed and presented their thoughts regarding mutating objects, and how it does not harm the application. Why should we complicate things when we can do them in simpler ways? Say, if we have object money and it dies, we do not need a second monkey to track the change? A lot of people would argue that monkey.isDead = true should solve our problem.

  1. When should I consider using Immutable JS?

You should use Immutable JS in the following...