Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering React Native

You're reading from   Mastering React Native Learn Once, Write Anywhere

Arrow left icon
Product type Paperback
Published in Jan 2017
Publisher Packt
ISBN-13 9781785885785
Length 496 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Eric Masiello Eric Masiello
Author Profile Icon Eric Masiello
Eric Masiello
Jacob Friedmann Jacob Friedmann
Author Profile Icon Jacob Friedmann
Jacob Friedmann
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Building a Foundation in React FREE CHAPTER 2. Saying HelloWorld in React Native 3. Styling and Layout in React Native 4. Starting our Project with React Native Components 5. Flux and Redux 6. Integrating with the NYT API and Redux 7. Navigation and Advanced APIs 8. Animation and Gestures in React Native 9. Refactoring for Android 10. Using and Writing Native Modules 11. Preparing for Production 12. React Native Tools and Resources

Wiring up our Redux data flow


Now that we've had a look at what this data will look like, let's start writing some code. From the terminal, navigate to the root directory of RNNYT and run the following:

npm install redux react-redux redux-logger --save

We already discussed redux and react-redux at length in Chapter 5, Flux and Redux. redux-logger is a popular Redux middleware useful for observing changes to your app's Redux state tree from your browser's console. You may find it useful as you work through this chapter or future chapters.

Next, let's reorganize our files and folders to match one of the more conventional project structures seen in Redux applications. Create the following directories within your src directory:

  • actions

  • config

  • containers

  • reducers

  • util

Each folder will house different parts of our application.

Note

We've opted to organize our code by role. That is to say, we'll be grouping all our action creators in the actions folder, containers in the containers folder, and so forth...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime