Introduction to the newline guide to building a React App with MobX State Tree

Application Overview

State Management on the JavaScript ecosystem

State Management

What is MobX State Tree?

What will you learn in this course?

Will this course be for you?

Introduction

Introduction to the mental model of MobX State Tree

The Tree in MobX State Tree

Introduction to the store model of MobX State Tree

The Store Model

Introduction to the types in MobX State Tree

Types

Introduction to the model actions of MobX State Tree

Model Actions

Introduction to the model views of MobX State Tree

Model Views

Introduction to the store snapshots of MobX State Tree

Snapshots

Identifiers and references of MobX State Tree

Identifiers and References

Asynchronous Actions

Lifecycle Hooks

Concepts

Arrays in MobX State Tree

Maps

Working with nested stores in MobX State Tree

Nesting Stores

Optimistic Updates

Time Travel

Advanced Concepts

Overview of React and MobX State Tree

Combining MobX State Tree with React via Context and a custom Hook

Context and Hooks

Observable

React

Overview

Building Voyager

mobx-state-tree

In this course, we will create a complete React Application with the state management handled by MobX State Tree, a state container system that is built on MobX, a functional reactive state library.

MobX State Tree will give your application a solid structure and foundation for large-scale applications and for small applications that are expected to scale rapidly. In comparison to Redux, MobX State Tree outstands it in performance with much less boilerplate. MobX is one of the most popular Redux alternatives and it's used by companies all over the world, including Netflix, Grow, IBM, DAZN, Baidu, and more.

During this course, you'll learn:

* Types in MobX State Tree.
* How to create the architecture of a centralized store.
* How to mutate the state via actions that could be asynchronous or not, depending on if we need to perform network requests to persist data into a database via GraphQL.
* Understanding snapshots and how we can benefit from them to time-travel if a network request fails.
* Understanding how MobX State Tree makes use of observable properties and observers.
* Leveraging re-renders in your React Application to MobX observers for better performance optimizations.

By the end of this course, you will have the knowledge and skills that it takes to build a real-world, production-level React Application with a State Management with top-notch performance that can scale with ease.

In this course, we'll show you how to build a React App with MobX State Tree.

The newline Guide to Building a React App with MobX State Tree

How to integrate MobX State Tree within your React App

Dealing with asynchronous flows and time travel to preserve state on networking errors

How to create a scalable store using MobX State Tree

---
title: Maps
slug: maps-in-mobx-state-tree
description: Working with maps in MobX State Tree
role: "LESSON"
isPublicLesson: false
---

# Working with `Maps` in MobX State Tree

In MobX State Tree, we could use maps to create collections whose children are all of a uniformly declared type.

Lets take a look at an example. If you find it daunting, no worries. It's not really complex and you will eventually get used to doing this on a daily basis.

```js { actualFilename=src/maps.js endChar=1415 endLine=67 startChar=0 startLine=1 statedFilename=src/maps.js url=https&#x3A;//gitlab.com/fullstackio/books/newline-guide-to-building-a-react-app-with-mobx-state-tree/module_02/lesson_02.02/src/maps.js }
import { types, flow } from "mobx-state-tree";

const User = types
  .model("User", {
    id: types.identifier,
    name: types.string,
    lastName: types.string,
    age: types.number,
  })
  .views((self) => ({
    get fullName() {
      return `${self.name} ${self.lastName}`;
    },
  }))
  .actions((self) => ({
    updateName(name) {
      self.name = name;
    },
    updateLastName(name) {
      self.lastName = name;
    },
    updateAge(age) {
      self.age = age;
    },
  }));

const RootStore = types
  .model("RootStore", {
    users: types.map(User), // 1
    state: "idle",
  })
  .views((self) => ({
    findUserById(id) {
      // 3
      self.users.get(id);
    },
    userExists(id) {
      return self.user.has(id); // 2
    },
  }))
  .actions((self) => ({
    fetchUsers: flow(function* () {
      self.state = "fetching";
      let users;
      try {
        const data = yield fetchUsersFromBackend();
        users = yield data.json();
        self.state = "done";
      } catch (error) {
        console.error("Failed to fetch users", error);
        self.state = "error";
      }
      for (let i = 0; i < users.length; i++) {
        self.users.set(users[i].id, users[i]); // 3
      }
    }),
    addUser(user) {
      self.users.put(user); // 4
    },
    removeUser(id) {
      self.users.delete(id); // 5
    },
    removeAllUsers() {
      self.users.clear(); // 6
    },
  }));
```

Now that you took a look at the example, let's analyze the key points:

1.  `types.map(User)` is how we are defining our mapped collection of `User` type. Each of these `users` will contain all of the `properties`, `views`, and `actions` that are associated with its corresponding model. If the type stored in a map has an identifier, it is mandatory to store the child under that identifier in the map.
2.  You can check for the existence of any value in the map by using the standard JavaScript API for working with maps.
3.  Inserting an element into the map is handled via the standard JavaScript API for working with maps. The set method expects the first parameter, the key, to be the `identifier` of the model object stored as value if it's present on it.
4.  Inserting an element into the map is also handled via the standard JavaScript API for working with maps. The `put` method will also infer key from the `identifier` of the object stored if it has an `identifier`.
5.  Removing an element from the map is also handled via the standard JavaScript API for working with maps.
6.  If you'd like to remove all the elements from the map, you can do it via the standard JavaScript API for working with maps and MobX State Tree will take care of removing all references that are used across your store to make sure that no references remain lost in your store and that you're not accessing stale or outdated data.

Whenever you retrieve an element from a map or the full collection of elements that are contained within it, you will get them all with their respective full models; meaning that they will come with their `views`, and `actions` and other things that you might have added to them. If you would like to retrieve a standard JavaScript array with standard JavaScript primitives within it, you can do so by importing the helper method, `toJS`, from `mobx-state-tree` library and using it like `toJS(map)`. This will remove all MobX State Tree related things to the array. A good use case for this will be when you want to send data to the backend or via websocket; in those cases, you'd like to have the data as lean as possible. Let's take a look at a quick example:

```js { actualFilename=src/to-js.js endChar=498 endLine=30 startChar=0 startLine=1 statedFilename=src/to-js.js url=https&#x3A;//gitlab.com/fullstackio/books/newline-guide-to-building-a-react-app-with-mobx-state-tree/module_02/lesson_02.02/src/to-js.js }
import { types, toJS } from "mobx-state-tree";

const User = types
  .model("User", {
    id: types.identifier,
    name: types.string,
    lastName: types.string,
    age: types.number,
  })
  .views((self) => ({
    // ...
  }))
  .actions((self) => ({
    // ...
  }));

const RootStore = types
  .model("RootStore", {
    users: types.map(User),
  })
  .views((self) => ({
    // ...
    get leanMapToJS() {
      return toJS(self.users);
    },
  }))
  .actions((self) => ({
    // ...
  }));
```
