Book Image

Hands-On Design Patterns with React Native

By : Mateusz Grzesiukiewicz
Book Image

Hands-On Design Patterns with React Native

By: Mateusz Grzesiukiewicz

Overview of this book

React Native helps developers reuse code across different mobile platforms like iOS and Android. This book will show you effective design patterns in the React Native world and will make you ready for professional development in big teams. The book will focus only on the patterns that are relevant to JavaScript, ECMAScript, React and React Native. However, you can successfully transfer a lot of the skills and techniques to other languages. I call them “Idea patterns”. This book will start with the most standard development patterns in React like component building patterns, styling patterns in React Native and then extend these patterns to your mobile application using real world practical examples. Each chapter comes with full, separate source code of applications that you can build and run on your phone. The book is also diving into architectural patterns. Especially how to adapt MVC to React environment. You will learn Flux architecture and how Redux is implementing it. Each approach will be presented with its pros and cons. You will learn how to work with external data sources using libraries like Redux thunk and Redux Saga. The end goal is the ability to recognize the best solution for a given problem for your next mobile application.
Table of Contents (13 chapters)

The iterator pattern

In the previous section, we traversed many different collections, even nested ones. Now, it's time to learn more about the iterator pattern. This pattern especially shines if you plan to use the Redux Saga library.

If you jumped straight to this chapter, I highly advise you to read the section that introduces iterator patterns in Chapter 6, Data Transfer Patterns. That chapter also covers the Redux Saga library and generators.

To recap, in JavaScript, an iterator is an object that knows how to traverse items of a collection one at a time. It must expose the next() function, which returns the next item of a collection. The collection can be whatever it wants. It can even be an infinite collection, such as the Fibonacci numbers, as seen here:

class FibonacciIterator {
constructor() {
this.n1 = 1;
this.n2 = 1;
}
next() {
var...