How do MobX observables work?

MobX reacts to any existing observable property that is read during the execution of a tracked function . “reading” is dereferencing an object’s property, which can be done through “dotting into” it (eg. user.name ) or using the bracket notation (eg. user[‘name’] , todos[3] ) or destructuring (eg.

Read more

What are reactions in MobX?

Reactions are an important concept to understand, as it is where everything in MobX comes together. The goal of reactions is to model side effects that happen automatically . Their significance is in creating consumers for your observable state and automatically running side effects whenever something relevant changes.

Read more

What is observable in MobX React?

In The gist of MobX you have already seen the most important part of this integration: the observer HoC that you can wrap around a React component . observer is provided by a separate React bindings package you choose during installation. In this example, we’re going to use the more lightweight mobx-react-lite package.

Read more

What are MobX reactions?

The MobX triad is completed when we add Reactions into the mix. Having reactions is what triggers the reactivity in the system. A reaction implicitly tracks all the observables which are being used and then re-executes its logic whenever the depending observables change .

Read more

What is a MobX store?

The primary purpose of MobX is to simplify the management of Reactive State in your application . As your application scales, the amount of state you manage will also increase. This requires some techniques to break down your application state and divvy it up across a set of stores.

Read more