NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev · #2577 most downloaded on pub.dev
a simple yet powerful state management technique for Flutter
Last release 1 months ago
16 Aug 2026
Ships unpredictably
gaps range from 2 weeks to 2.5 years
Rarely documented
notes for 14 of 57 stable releases
Nothing withdrawn
no release was ever pulled
8 years old
90 releases · first in 2019
Nothing published for this version
Nothing published for this version
RM.injectNavigator is deprecated
RM.injectNavigator is deprecatedOne column per quarter.
Add ReactiveModel.isStateInitialized getter to check if the state has already initialized or not yet.
ReactiveModel.isStateInitialized getter to check if the state has already initialized or not yet.* update to dart3 * internal refactor
Now states_rebuilder use the navigation_builder package without any breaking change.
InjectedNavigation.states_rebuilder use the navigation_builder package without any breaking change.stateAsync coherent with setToWaiting.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
* Fix issues #265 #267 * Improve print log messages
Nothing published for this version
Add OnBuilder.createFuture and OnBuilder.createStream widgets.
OnBuilder.createFuture and OnBuilder.createStream widgets.OnBackNavigationScope widgetNothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add statesInterceptor to setState method.
statesInterceptor to setState method.setToIsIdle, setToIsWaiting, setToHasData, setToHasError methods.OnBuilder.create listener.ReactiveStatelessWidget.didMountWidget takes BuildContext as parameter.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
onSetState, onData, onError, onAfterState are all deprecated in favor to sideEffects parameter which takes a SideEffects object.(See issue #222).
RM.injectFormField and OnFormFiledFielder to injected input fields other than TextFiled (See issue #219).refreshToken method to IAuth interface. It is used to refresh token (See issue #228).isEnabled and isReadOnly to to InjectedTextEditing, and OnFormBuilder (See issue #229).TopStatelessWidget to replace TopAppWidget (See issue #232).InjectedTabPageView to work with tabs and pages (See issue #233).onSetState, onData, onError, onAfterState are all deprecated in favor to sideEffects parameter which takes a SideEffects object.(See issue #222).validator parameter in RM.injectTextEditing. validators is used instead.middleSnapState in favor to stateInterceptoronCRUD (in RM.injectedCRUD) in favor to OnCRUDSideEffectsSee the detailed change log Here
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
myState.rebuilder,myState.whenRebuilder, myState.whenRebuilderOr are deprecated in favor to myState.rebuild, myState.rebuild.onAll, myState.rebuild.on…
OnReactive widget for implicit subscription:final counter = 0.inj();
// inWidget tree
OnReactive(
() => Text(counter.state.toString()); // will rebuild if the state of counter changes
)
ReactiveStatelessWidget abstract widget for implicit subscription:///All states consumed in a descendant widget of this widget will be listened to.
class MyWidget extends ReactiveStatelessWidget{
@override
Widget build(BuildContext context) {
return Builder(
builder: (context){
return Text(counter.state.toString());
}
);
}
}
Add OnBuilder, OnAuthBuilder, OnCRUDBuilder, OnAnimationBuilder,OnScrollBuilder ,OnFormBuilder, OnFormSubscriptionBuilder, OnTabBuilder widget and their method equivalent: myState.rebuild, myState.rebuild.onAuth, myState.rebuild.onCRUD, myState.rebuild.onAnimation, myState.rebuild.onScroll, myState.rebuild.onForm, myState.rebuild.onFormSubscription, myState.rebuild.onTab,
myState.rebuilder,myState.whenRebuilder, myState.whenRebuilderOr are deprecated in favor to myState.rebuild, myState.rebuild.onAll, myState.rebuild.onOr,
Add InjectedPageTab to easily deal with page and tab views.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add InjectedAnimation.resetAnimation method reset the global duration, curve and repeats of the animation.
InjectedAnimation.resetAnimation method reset the global duration, curve and repeats of the animation.InjectedAnimation.triggerAnimation to force animation to restart from the lower bound.Nothing published for this version
Nothing published for this version
Add shouldAutoStart parameter to RM.injectedAnimation (See issue #186).
shouldAutoStart parameter to RM.injectedAnimation (See issue #186).setCurve and setReverseCurve to the InjectedAnimation. Useful for staggered animation (See issue #186).InjectedAnimation.refresh and InjectedAnimation.triggerAnimation return a future that resolves when the started animation ends.PersistState.shouldRecreateTheState (see issue #192).Nothing published for this version
* Fix onAuthStream issue #170
Deprecate TopAppWidget.waitFor in favor of TopAppWidget.ensureInitialization.
InjectedCRUD and InjectedAuth, getRepoAs is now sync.InjectedAnimation InjectedScrolling, InjectedTextEditing and InjectedForm.TopAppWidget.waitFor in favor of TopAppWidget.ensureInitialization.Test:
setUp method.All onError callbacks in On and OnCombined expose a refresher to retry the last async function that causes the exception.
RM.injectComputed is removedonError callbacks in On and OnCombined expose a refresher to retry the last async function that causes the exception.fullscreenDialog and maintainState parameters to the navigatorSee the detailed change log Here
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
reinject and getAsReactive to Injector. 2- Remove the following parameters:(Breaking changes)
Injected.persist is a function instead of a simple objectpersistStateProvider, catchPersistError and debugPrintOperations to PersistState class. ```dart
final model = RM.inject<Model>(
() => 0,
persist:()=> PersistState(
key: '__model_Key__',
toJson: (state) => json.encode(state),
fromJson: (json) => json.decode(json),
onError: (err, stack){
//If the persistance fails, the error is captured here, and the state is undone to the
//last valid state
}
//For this state the default persistance provider is overridden.
persistStateProvider: MyAnOtherPersistanceProvider()
//Print an informative message on the Read, Write, Delete operations
debugPrintOperations: true,
//Catch read, delete Exceptions
catchPersistError: true,
),
);
Since errors are not created to be caught, states_rebuilder will not catch errors unless the parameter [StatesRebuilderConfig.shouldCatchError] is true. Instead, Exceptions are intended to be caught. Your costume error/exception classes must implement Exception not Error.
As this may leads the app to break, to fix just search for all extends Error { and replace with implements Exception {
Introduction of Injected.inherit and Inject.reInherit methods for widget-wise injection. Similar to InheritedWidget.
Experimental with Injected.listen as possible substitution of Injected.rebuilder, Injected.whenRebuilder and Injected.whenRebuilderOr.
RM.navigate for simple navigation.
Now, we use:MaterialApp(
navigatorKey : RM.navigate.navigatorKey,
//
)
//to navigate:
* RM.navigator.to(Page1());
* RM.navigator.toNamed('/page1');
* RM.navigator.toReplacement(Page1());
* RM.navigator.toReplacementNamed('/page1');
* RM.navigator.toAndRemoveUntil(Page1(), '/page2');
* RM.navigator.pushNamedAndRemoveUntil('/page1', '/page2');
* RM.navigator.back();
* RM.navigator.backUntil('/page2');
* RM.navigator.backAndToNamed('/page2');
//To show dialogs, menu and bottom sheets
* RM.navigator.toDialog => showDialog
* RM.navigator.toCupertinoDialog => showCupertinoDialog
* RM.navigator.toBottomSheet => showModalBottomSheet
* RM.navigator.toCupertinoModalPopup => showCupertinoModalPopup
//To show Scaffold related snackBars, bottom sheets and drawers
* RM.scaffoldShow.bottomSheet => Scaffold.of(context).showBottomSheet,
* RM.scaffoldShow.snackBar => Scaffold.of(context).showSnackBar,
* RM.scaffoldShow.openDrawer => Scaffold.of(context).openDrawer,
* RM.scaffoldShow.openEndDrawer => Scaffold.of(context).openEndDrawer,
RM.navigator, RM.Scaffold and RM.show.shouldRebuild parameter to StateBuilder and other widgets.
Now StateBuilder will build only if the exposed model hasData (For performance reason).
This make cause some unexpected behavior.
To all the widget to rebuild on other state (onWaiting, onError), you can:
WhenRebuilderOr widget. Or,shouldRebuild parameterStateBuilder(
observe: ()=>MyReactiveModel(),
shouldRebuild: (rm)=> true,
builder: (context, rm){
//--
}
)
StateWithMixinBuilder has changed and named constructors have been added.Injector(
inject: [Inject(() => Model())],
builder: (context) {
//Get the injected ReactiveModel and subscribe this ContextBuilder to it.
final rm = RM.get<Model>(context: context);
return rm.whenConnectionState(
onIdle: () => Text('idle'),
onWaiting: () => Text('waiting'),
onError: (e) => Text('${e.message}'),
onData: (d) => Text(d.counter.toString()),
);
},
);
Add possibility to skip onWaiting while calling setState. (#109)
Add two static flags debugError and debugErrorWithStackTrace to console log states__rebuilder related errors.
Improve logics and docs.
refresh method to the ReactiveModel object. See morenotify method to the ReactiveModel object.future and stream methods.debounceDelay and throttleDelay to setState method.RMKey.get method.final rm = RM.get<T>(context: context);
After: one have to use one of the four observer widgets
StateBuilder(
observe : ()=> RM.get<T>(),
builder : (context, rm ){
//...
}
)
As consequence Injector.reinject is removed
setValue, value, getFuture, getStream and getSetState.
All the functionalities of the removed API are done with setState, future, stream methods.see more detailsSateBuilder, WhenRebuild, WhenRebuilderOr, and OnSEtStateListener.class ModelA{
}
class ModelB {
ModelB(){
RM.get<ModelA>().listenToRM((ReactiveModel<ModelA> modelARM)){
if(modelARM.hasError){
//....
}else if (modelARM.hasData){
//...
}
//or you can use whenConnectionState
}
}
}
The listenToRM return a void callBack to be used for unsubscription.valueAsync to obtained the state of a ReactiveModel as future.Inject.previous. #47 see more detailsReactiveModels:IN.get<T>()//To consume the pure registered instance;
RM.get<T>(); //to get the ReactiveModel instance of type T.
RM.create<T>(myModel);// to create a local ReactiveModel.
RM.future<T>(myFuture);// to create a local future ReactiveModel.
RM.stream<T>(myStream);// to create a local stream ReactiveModel.
RM.getSetState<T>(fn); // to get the ReactiveModel T and call setState method
ReactiveModel.future and ReactiveModel.stream, to handle state notification of immutable objects.see more details.onData (issue #78) and onError to the ReactiveModel.RM.printActiveRM to print the ReactiveModel has is sending the notification.reinjectOn parameters to Injector widgets. It takes a list of ReactiveModel, and it re-injects the registered models whenever any of the ReactiveModels in the reinjectOn parameters emits a notification. issue #47.example of injected stream:
final multiplierRM = ReactiveModel.create(1);
Widget builder(BuildContext context){
return Injector(
inject: [Inject.stream(() => Stream.periodic(Duration(seconds: 1), (num) => multiplierRM * num))],
//Listen to multiplierRM and reinject the stream whenever multiplierRM emits a notification
reinjectOn: [multiplierRM],
builder: (context) {
///
///
},
);
}
The stream emits: 1, 2, 3, 4, ... because multiplierRM = 1.
when the value multiplierRM is set to 2:
multiplierRM.setValue(()=>2);
The stream subscription is cancelled and an new subscription is established that emits the values : 2, 4, 6, 8 ..... (multiplierRM = 2). Now decedent widgets can subscribe to the stream and rebuild whenever the stream emits a value.
This works for injected streams, futures and vanilla dart classes.
Add watch parameter to ReactiveModel.stream constructor. issue 61
refactor code to improve performance.
ReactiveModel<T>.stream(T stream) and ReactiveModel<T>.future(T future) to create a ReactiveModel from a stream or future.toString method of the ReactiveModel to give an informative debug print.ReactiveModel<T>() factory constructor. it is equivalent to Injector.getAsReactive(<T>). You will save nine key stroke and it looks more readable.//You can use the long form
final fooRM = Injector.getAsReactive<Foo>();
//Or the new way:
final fooRM = ReactiveModel<Foo>();
for example instead of :
StateBuilder<Foo>(
models:[Injector.getAsReactive<Foo>()],
builder:(context, fooRM){
}
)
you write:
StateBuilder<Foo>(
models:[ReactiveModel<Foo>()],
builder:(context, fooRM){
}
)
shouldOnInitState to OnSEtStateListener: Usually onSetState and its equivalent onData, onError are invoked only if the observable reactive model emits a notification. This means they are not invoked in the initState method. shouldOnInitState is an optional bool parameter and when se to true the onSetState method will be called from the initState method.onData to WhenRebuilderOrresetToIdle and resetToHasData methods to the ReactiveModel.
use case examples:getAsReactive so that each time the reactive model is obtained, it will be obtained with the desired asynchronous state, whatever its value before.final fooRM = Injector.getAsReactive<Foo>()..resetToIdle();
//you can combine it with asNew
final fooRM = Injector.getAsReactive<Foo>().asNew('mySeed')..resetToIdle();
fooRM.setState(
(s) => s.someMethod(),
onError: (context, error) async {
//awaiting the alert dialog
await showDialog(
context: context,
builder: (context){
///
}
);
//clearing the error.
fooRM.resetToHasData();
},
)
Injector.enableTestMode static bool field. Set it to true in tests to inject fake dependency.
ex:
Let's suppose we have the widget.Import 'my_real_model.dart';
class MyApp extends StatelessWidget {
@override
Widget build(BuildContext context) {
return Injector(
inject: [Inject(() => MyRealModel())],
builder: (context) {
final myRealModelRM = Injector.getAsReactive<MyRealModel>();
// your widget
},
);
}
}
MyApp widget depends on MyRealModel.
To mock MyRealModel and test MyApp we set Injector.enableTestMode to true :
testWidgets('Test MyApp class', (tester) async {
//set enableTestMode to true
Injector.enableTestMode = true;
await tester.pumpWidget(
Injector(
//Inject the fake model and register it with the real model type
inject: [Inject<MyRealModel>(() => MyFakeModel())],
builder: (context) {
//In my MyApp, Injector.get or Inject.getAsReactive will return the fake model instance
return MyApp();
},
),
);
//My test
});
//fake model implement real model
class MyFakeModel extends MyRealModel {
// fake implementation
}
See real test of the counter_app_with_error and counter_app_with_refresh_indicator.
tag and onWaiting parameters to OnSetStateListener widget.tag parameter to WhenRebuild and WhenRebuildOr widgetssetValue and setState. Now setValue has all the functionalities of setState.Injector.env and Inject.interface named constructor so that you can register under different environments.ex:
//abstract class
abstract class ConfigInterface {}
// first prod implementation
class ProdConfig extends ConfigInterface {}
//second dev implementation
class DevConfig extends ConfigInterface {}
//enum for defined flavor
enum Flavor { Prod, Dev }
void main() {
//Choose yor environment flavor
Injector.env = Flavor.Dev;
runApp(
Injector(
inject: [
//Register against an interface with different flavor
Inject<ConfigInterface>.interface({
Flavor.Prod: ()=>ProdConfig(),
Flavor.Dev:()=>DevConfig(),
}),
],
builder: (_){
return MyApp(
appTitle: Injector.get<ConfigInterface>().appDisplayName;
);
},
)
);
}
StateBuilder<T>, WhenRebuilder<T> and OnSetStateListener<T> observer widgets can be set to observer many observable reactive models. The exposed model instance depends on the generic parameter T.
ex://first case : generic model is ModelA
StateBuilder<ModelA>(
models:[modelA, modelB],
builder:(context, exposedModel){
//exposedModel is an instance of ReactiveModel<ModelA>.
}
)
//second case : generic model is ModelB
StateBuilder<ModelB>(
models:[modelA, modelB],
builder:(context, exposedModel){
//exposedModel is an instance of ReactiveModel<ModelB>.
}
)
//third case : generic model is dynamic
StateBuilder(
models:[modelA, modelB],
builder:(context, exposedModel){
//exposedModel is dynamic and it will change over time to hold the instance of model that emits a notification.
//If modelA emits a notification the exposedModel == ReactiveModel<ModelA>.
//Wheres if modelB emits a notification the exposedModel == ReactiveModel<ModelB>.
}
)
WhenRebuilderOr. It is equivalent to WhenRebuilder but with optional onIdle, onWaiting and onError parameters and with required default builder.ReactiveModel<T>.create(T value) to create a ReactiveModel from a primitive value. The created ReactiveModel has the full power the other reactive models created using Injector have.
ex: This is a simple counter app:class App extends StatelessWidget {
//Create a reactiveModel<int> with initial value and assign it to counterRM filed.
final counterRM = ReactiveModel.create(0);
@override
Widget build(BuildContext context) {
return MaterialApp(
home: Scaffold(
body: Center(
// Subscribe StateBuilder widget ot counterRM
child: StateBuilder(
models: [counterRM],
builder: (context, _) {
return Text('${counterRM.value}');
},
),
),
floatingActionButton: FloatingActionButton(
child: Icon(Icons.add),
//set the value of the counterRM and notify observers.
onPressed: () => counterRM.setValue(() => counterRM.value + 1),
),
),
);
}
}
WhenRebuilder widget. It is a shortcut of using SateBuilder to subscribe to an observable model and use ReactiveModel.whenConnectionState method to exhaustively switch over all the possible statuses of connectionState.instead of:
Widget build(BuildContext context) {
return StateBuilder<PlugIn1>(
models: [Injector.getAsReactive<PlugIn1>()],
builder: (_, plugin1RM) {
return plugin1RM.whenConnectionState(
onIdle: () => Text('onIDle'),
onWaiting: () => CircularProgressIndicator(),
onError: (error) => Text('plugin one has an error $error'),
onData: (plugin1) => Text('plugin one is ready'),
);
},
);
}
You use :
@override
Widget build(BuildContext context) {
return WhenRebuilder<PlugIn1>(
models: [Injector.getAsReactive<PlugIn1>()],
onIdle: () => Text('onIdle'),
onWaiting: () => CircularProgressIndicator(),
onError: (error) => Text('plugin one has an error $error'),
onData: (plugin1) => Text('plugin one is ready'),
);
}
As a good side effect of using WhenRebuilder, you can subscribe to many observable models and a combination status is exposed so that onData will not be invoked only after all observable models have data.
ex:
final plugin1RM = Injector.getAsReactive<PlugIn1>();
final plugin2RM = Injector.getAsReactive<PlugIn2>();
@override
Widget build(BuildContext context) {
return WhenRebuilder<PlugIn1>(
models: [plugin1RM, plugin2RM],
onIdle: () => Text('onIDle'),
//onWaiting is called if any models is in the waiting state
onWaiting: () => CircularProgressIndicator(),
// onError will be called with the thrown error, if any of the observed models throws.
onError: (error) => Text('plugin1 or plugin2 has an error $error'),
//onData is called when all observable models have data
onData: (plugin1) => Text('plugin1 and plugin2 are both ready'),
);
}
Add OnSetStateListener widget to handle side effects. It subscribes to a list of observable models and listen to them and execute the corresponding onData or onError side effects.
Add value getter and ReactiveModel.setValue method. They are the counterpart of the state getter and ReactiveModel.setState method respectively. They are more convenient to use with primitive values and immutable objects.
Add ReactiveModel.asNew([dynamic seed]) to create new reactive instance.
Replace setState.joinSingletonWith in with the bool parameter setState.joinSingleton.
A huge Refactor of the code. I have written the code from the ground using Test Driven Design principles. Now the cod is cleaner, shorter, and more effective.
StatesRebuilderDebug.printInjectedModel() to debugPrint all registered model in the service locator.StatesRebuilderDebug.printObservers(observable) to )debugPrint all subscribed observers to the provided observable.onData(BuildContext, T) parameter to setState method.
It is a shortcut to:onSetState(context){
if(reactiveModel.hasData){
.....
}
}
Inject.get for injected streams and future will no longer throw, it will return the the current value.whenConnectionState is defined, catchError is set true automatically.watch parameter to StateBuilder widget and. watch allows to link the rebuild process to the variation of a set of variables.(Experimental feature).getAsModel and hasState.whenConnectionState method to the ReactiveModel. IT exhaustively switch over all the possible statuses of connectionState. Used mostly to return a Widget. (Pul request of ResoCoder).isIdle getter to the ReactiveModel as a shortcut to :
connectionState == ConnectionState.noneisWaiting getter to the ReactiveModel as a shortcut to :
connectionState == ConnectionState.waitingonError(BuildContext, dynamic) parameter to setState method.joinSingletonToNewData parameter to setState method.1- Add the following features: (See readme fille).
onSetState and onRebuildState parameters to the StateBuilder.StateBuilder.JoinSingleton, inheritedInject, initialCustomStateStatus parameters to Injectreinject and getAsReactive to Injector.
2- Remove the following parameters:(Breaking changes)tagID parameter from StateBuilder.
beforeStateBuilder(
builder: (BuildContext context, String tagID){
// code
}
)
after
StateBuilder<T>(
models: [firstModel, secondModel],
builder: (BuildContext context, ReactiveModel<T> model){
/// No more need for the `tagID` because the `context` is used as `tagID`.
/// the model is the first instance (firstModel) in the list of the [models] parameter.
/// If the parameter [models] is not provided then the model will be a new reactive instance
/// See readme file for more information
}
)
Injector.builder method.
beforeInjector(
builder: (BuildContext context, T model){
// code
}
)
after
Injector(
builder: (BuildContext context){
// no need for model parameter. It has less boilerplate.
}
)
Injector.getAsModel, StateBuilder.viewModel and StatesRebuilder.hasState are deprecated, and replaced by Injector.getAsReactive, StateBuilder.models and StatesRebuilder.hasObservers respectively.1- Add onSetState parameter to the setState method to define a callback to be executed after state mutation.
The callBack takes the context so you can push/pop routes, show dialogs or snackBar. (see example folder).
2- Add catchError parameter to the setState method to define whether to catch error while mutining the state or not.(see example folder). If an error is thrown, hasError getter is true and the error can be obtained via the error getter (see point 5 below).
3- Add the getter connectionState to the ModelStatesRebuilder<T>to get the asynchronous status of the state. it can be ConnectionState.none before executing the Future, ConnectionState.waiting while waiting for the Future and ConnectionState.done after resolving the Future.
4- Add the field stateStatus to the ModelStatesRebuilder<T> class. It allows defining a custom status of the state other than those defined by the connectionState getter.
5- add the getter hasError, hasData and error to the ModelStatesRebuilder<T> class.
6- Change the name blocs to models.
7- Refactor the code and fix bugs.
8- Update docs and examples.
watch parameter to setState method and Inject.stream constructor. watch allows to link the rebuild process to the variation of a set of variables.Injector.getAsModel method. When called with the context parameter, the calling widget is automatically registered as a listener.setState(Function(state)) to mutate the state and update the dependent the views from the UI.StatesRebuilder to get reactivity.Inject.future which take a future and update dependents when future completes.Inject.stream which take a steam and update dependents when stream emits a value.Injector.get or Injector.getAsModel now throws if no registered model is found. This can be silent by setting the parameter silent to trueisLazy of the Inject widget to false.afterInitialBuild and afterRebuild parameters to the StateBuilder, StateWithMixinBuilder and Injector widgets. afterInitialBuildandafterRebuild` are callBack to be executed after the widget is mounted and after each rebuild.ObservableService and hasState instead of Observable and hasObserver, because the latters are widely used and can lead to conflicthasStates getter to check if the StatesRebuilder object has listener.inject parameter to the Injector widget as an alternative to the models parameter. With inject you can register models using interface Type.observable interface. Any service class can implement it to notify any ViewModel to rebuild its corresponding view.appLifeCycle argument to Injector to track the life cycle of the app.rebuildFromStreams.Streaming classInjector takes (BuildContext context, T model) where T is the generic type.rebuildFromStreams method.Injector for Dependency Injection.stateID and replace it by tag parameter. tag is optional and many widgets can have the same tag.rebuildStates() when called without parameters, it rebuilds all widgets that are wrapped with StateBuilder and StateWithMixinBuilder.StateBuilder has an automatically generated cached address. It is stored in the second parameter of the builder, initState, dispose, and other closures. You can call it inside the closures to rebuild that particular widget.StateWithMixinBuilder widget to account for some of the most used mixins.withTickerProvider parameter to StateBuilder widget.BlocProviderto provide your BloCs.StateBuilder widgets.rebuildStates now has only one positioned parameter of List<dynamic>.rebuildStates is given without parameter, it will rebuild all widgets that have stateID.Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →