MobX CodeGen은 Flutter 및 Dart의 MobX 상태 관리 라이브러리를 위한 코드 생성 도구입니다. 개발자가 클래스와 필드에 @observable, @computed, @action를 주석으로 추가함으로써 반응형 상태 관리를 위한 빌더플레이트 코드를 자동으로 생성할 수 있습니다. 이는 수동 작업을 줄이고 반복적인 패턴을 제거하여 코드 가독성을 향상시킵니다. 이 패키지는 최소한의 설정으로 Store 클래스를 만들 수 있도록 지원하며, 플랫폼 간 상태 처리를 단순화합니다.
MobX is a state-management library that makes it simple to connect the
reactive data of your application with the UI. This wiring is completely automatic
and feels very natural. As the application-developer, you focus purely on what reactive-data
needs to be consumed in the UI (and elsewhere) without worrying about keeping the two
in sync.
It's not really magic but it does have some smarts around what is being consumed (observables)
and where (reactions), and automatically tracks it for you. When the observables
change, all reactions are re-run. What's interesting is that these reactions can be anything from a simple
console log, a network call to re-rendering the UI.
MobX has been a very effective library for the JavaScript
apps and this port to the Dart language aims to bring the same levels of productivity.
Sponsors
We are very thankful to our sponsors to make us part of their Open Source Software (OSS) program. [Become a sponsor]
For a deeper coverage of MobX, do check out MobX Quick Start Guide. Although the book uses the JavaScript version of MobX, the concepts are 100% applicable to Dart and Flutter.
Core Concepts
At the heart of MobX are three important concepts: Observables, Actions and Reactions.
Observables
Observables represent the reactive-state of your application. They can be simple scalars to complex object trees. By
defining the state of the application as a tree of observables, you can expose a reactive-state-tree that the UI
(or other observers in the app) consume.
A simple reactive-counter is represented by the following observable:
import'package:mobx/mobx.dart';
final counter = Observable(0);
More complex observables, such as classes, can be created as well.
On first sight, this does look like some boilerplate code which can quickly go out of hand!
This is why we added mobx_codegen to the mix that allows you to replace the above code with the following:
Note the use of annotations to mark the observable properties of the class. Yes, there is some header boilerplate here
but its fixed for any class. As you build more complex classes this boilerplate
will fade away and you will mostly focus on the code within the braces.
Note: Annotations are available via the mobx_codegen package.
Readonly
If you want to reduce your code you may want to swap @observable for @readonly.
For every private variable it generates a public getter such that the client of your store
can't change its value. Read more about it here
Computed Observables
What can be derived, should be derived. Automatically.
The state of your application consists of core-state and derived-state. The core-state is state inherent to the domain you are dealing with. For example, if you have a Contact entity, the firstName and lastName form the core-state of Contact. However, fullName is derived-state, obtained by combining firstName and lastName.
Such derived state, that depends on core-state or other derived-state is called a Computed Observable. It is automatically kept in sync when its underlying observables change.
In the example above fullName is automatically kept in sync if either firstName and/or lastName changes.
Actions
Actions are how you mutate the observables. Rather than mutating them directly, actions
add a semantic meaning to the mutations. For example, instead of just doing value++,
firing an increment() action carries more meaning. Besides, actions also batch up
all the notifications and ensure the changes are notified only after they complete.
Thus the observers are notified only upon the atomic completion of the action.
Note that actions can also be nested, in which case the notifications go out
when the top-most action has completed.
final counter = Observable(0);
final increment = Action((){
counter.value++;
});
When creating actions inside a class, you can take advantage of annotations!
Reactions complete the MobX triad of observables, actions and reactions. They are
the observers of the reactive-system and get notified whenever an observable they
track is changed. Reactions come in few flavors as listed below. All of them
return a ReactionDisposer, a function that can be called to dispose the reaction.
One striking feature of reactions is that they automatically track all the observables without any explicit wiring. The act of reading an observable within a reaction is enough to track it!
The code you write with MobX appears to be literally ceremony-free!
ReactionDisposer autorun(Function(Reaction) fn)
Runs the reaction immediately and also on any change in the observables used inside
fn.
import'package:mobx/mobx.dart';
final greeting = Observable('Hello World');
final dispose = autorun((_){
print(greeting.value);
});
greeting.value = 'Hello MobX';
// Done with the autorun()dispose();
// Prints:// Hello World// Hello MobX
Monitors the observables used inside the predicate() function and runs the effect() when
the predicate returns a different value. Only the observables inside predicate() are tracked.
import'package:mobx/mobx.dart';
final greeting = Observable('Hello World');
final dispose = reaction((_) => greeting.value, (msg) => print(msg));
greeting.value = 'Hello MobX'; // Cause a change// Done with the reaction()dispose();
// Prints:// Hello MobX
Monitors the observables used inside predicate() and runs the effect()when it returns true. After the effect() is run, when automatically disposes itself. So you can think of when as a one-timereaction. You can also dispose when() pre-maturely.
import'package:mobx/mobx.dart';
final greeting = Observable('Hello World');
final dispose = when((_) => greeting.value == 'Hello MobX', () => print('Someone greeted MobX'));
greeting.value = 'Hello MobX'; // Causes a change, runs effect and disposes// Prints:// Someone greeted MobX
Similar to when but returns a Future, which is fulfilled when the predicate() returns true. This is a convenient way of waiting for the predicate() to turn true.
One of the most visual reactions in the app is the UI. The Observer widget (which is part of the flutter_mobx package), provides a granular observer of the observables used in its builder function. Whenever these observables change, Observer rebuilds and renders.
