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

Declarative data fetching

As mentioned earlier, GraphQL is a query language that lets you define what the response of an API looks like by how you structure your query. This is a more declarative approach to data fetching than you see in other APIs. Not only is it a query language, but it also provides a runtime to fulfill those queries based on your existing data. Also, not only can you use GraphQL to fetch data with queries, but you can also send mutate data by using mutations.

When you want to use GraphQL, the API that you're using for data fetching should support GraphQL. This means the server should have a schema that describes which operations (that is, queries, mutations, or subscriptions) are allowed and which data fields can be requested. Every operation that is described in the schema for a GraphQL server can be executed by sending a document containing these operations. Other than with REST APIs, you have complete control over the shape of your data as you define...