Book Image

React and React Native - Fourth Edition

By : Adam Boduch, Roy Derks, Mikhail Sakhniuk
Book Image

React and React Native - Fourth Edition

By: Adam Boduch, Roy Derks, Mikhail Sakhniuk

Overview of this book

Over the years, React and React Native has proven itself among JavaScript developers as a popular choice for a complete and practical guide to the React ecosystem. This fourth edition comes with the latest features, enhancements, and fixes to align with React 18, while also being compatible with React Native. It includes new chapters covering critical features and concepts in modern cross-platform app development with React. From the basics of React to popular components such as Hooks, GraphQL, and NativeBase, this definitive guide will help you become a professional React developer in a step-by-step manner. You'll begin by learning about the essential building blocks of React components. As you advance through the chapters, you'll work with higher-level functionalities in application development and then put your knowledge to work by developing user interface components for the web and native platforms. In the concluding chapters, you'll learn how to bring your application together with robust data architecture. By the end of this book, you'll be able to build React applications for the web and React Native applications for multiple mobile platforms.
Table of Contents (36 chapters)
1
Part 1 – React
15
Part 2 – React Native
31
Part 3 – React Architecture

Container components

In this section, you're going to learn about the concept of container components. This is a common React pattern, and it brings together many of the concepts that you've learned about state and properties.

The basic premise of container components is simple: don't couple data fetching with the component that renders the data. The container is responsible for fetching the data and passing it to its child component. It contains the component responsible for rendering the data.

The idea is that you should be able to achieve some level of substitutability with this pattern. For example, a container could substitute its child component. Or a child component could be used in a different container.

Let's look at the container pattern in action, starting with the container itself:

import * as React from "react";
import MyList from "./MyList";
 
function fetchData() {
  return new Promise((resolve) => {
&...