mobx 0.3.6-alpha

MobX is a library for reactively managing the state of your applications. Use the power of observables, actions, and reactions to supercharge your Dart and Flutter apps.

0.3.6-alpha

• Experimenting with the @store annotation for simplified Store creation

0.3.5 - 0.3.5+1

• Fixed a bug where the ObservableFuture<T> would not show the correct status. This was happening because of the lazy evaluation strategy. We are now being eager in creating the status and monitoring the inner Future<T> immediately.
• Upgraded test_coverage

0.3.3+1 - 0.3.4

• Removed the @experimental annotations for Observable{Future,Stream} and reaction.
• Removed the dependency on the meta package.
• Some formatting changes
• Reporting update or change only when the new value is different than the old value. This is mostly for observable collections like list, set, map.

0.3.3

• Wrapping all collection setters in conditional action wrappers. This removes the need to wrap collection mutating methods in explicit actions.

0.3.0 - 0.3.2+3

• API changes introduced to the enforceActions setting of ReactiveConfig. It is now called writePolicy and the enum EnforceActions has been renamed to ReactiveWritePolicy.
• Also introducing a readPolicy setting on ReactiveConfig. It is an enumeration with two values:
• Removing the "strict-mode" text in the exception message when the ReactiveWritePolicy is violated. This was a vestige from the mobx.js world.
• Exposing a boolean isWithinBatch on ReactiveContext, which tells if the current code is running inside a batch. This is used to conditionally apply an action-wrapper for mobx_codegen-generated setters.
• Introduced an action-wrapper called conditionallyRunInAction() that runs the given function in an action only when outside a batch.
• Increasing test coverage

enum ReactiveReadPolicy { always, never }

0.2.1+2

• Improving test coverage

0.2.1+1

• README updates

0.2.1

• An internal change was made to support the new restrictions around non-covariant type variables in superinterfaces. This was causing compile errors in the Flutter beta/dev/master channels.

0.2.0

• A breaking change has been introduced to the use of the Store type. Previously it was meant to be used as an interface, which has now changed to a mixin. Instead of doing:

abstract class UserBase implements Store {}

You now do:

abstract class UserBase with Store {}

This allows us to add more convenience methods to the Store mixin without causing any breaking change in the future. With the current use of the interface, this was not possible and was limiting the purpose. Store was just a marker interface without any core functionality. With a mixin, it opens up some flexibility in adding more functionality later.

• All the docs and example code have been updated to the use of the Store mixin.