Aus öffentlichen Paketdaten erstellte Orientierung.
Reduced bietet eine einheitliche Oberfläche für zentrale Zustandsverwaltungsfunktionen in beliebten Flutter-Zustandsverwaltungs-Frameworks. Es vereinfacht die Integration durch eine konsistente API zum Verwalten von Zuständen, Handhaben von Abhängigkeiten und Reagieren auf Änderungen, unabhängig vom zugrundeliegenden Framework. Für Entwickler, die Flexibilität ohne Boilerplate suchen, wurde Reduced entwickelt, um Komplexität zu verbergen, während Leistung und Skalierbarkeit erhalten bleiben. Ideal für Projekte, die zwischen mehreren Zustandsverwaltungslösungen wechseln oder diese kombinieren möchten.
Anwendungsfälle
Zustandsverwaltung über mehrere Frameworks vereinfachen
Nahtlose Integration mit bestehenden Zustandslösungen
Geeignet für
Entwickler, die mehrere State-Management-Bibliotheken verwenden
Projekte, die flexible Zustandsarchitektur erfordern
Teams, die die Komplexität reduzieren möchten
Anwendungen, die zukunftssichere Zustandsdesign benötigen
Prototyping mit austauschbaren Zustandsmustern
Hinweise
Kann aufgrund der Abstraktionsschicht geringfügige Overhead verursachen
Am besten geeignet für mittelgroße bis große Anwendungen
Erfordert Verständnis der zugrundeliegenden Zustandskonzepte
Beschränkt auf unterstützte Backend-Systeme für Zustandsverwaltung
Nicht empfehlenswert für einfache Einmalanwendungen
Original-README
Originaler README-Schnappschuss aus dem verknüpften Quell-Repository. Aktuelle Inhalte finden Sie im Repository.
reduced
Unified facade for the basic features of state management frameworks:
Read a current state value.
Update a current state value.
Callbacks with value semantics
The app logic based mainly on these features should remain as independent as possible from the state management framework used. Therefore, the app logic needs a neutral state management API and an implementation of this API for the state management framework used.
The former is provided by this package. The latter is provided by other packages listed at the end of the README.
Features
The 'reduced' facade covers the following features of a state management framework:
Instead of writing the state value directly, the facade provides a process method that accepts a called event as a parameter.
In the process method the event is executed with the current state value as a parameter and the return value of the event is stored as the new state value.
typedefSnapshotToPropsMapper<S, P> = P Function(
StoreSnapshot<S> snapshot,
String? routeName,
);
A SnapshotToPropsMapper is a Function that uses the snapshot and the routeName parameters to map the current state of a store into a derived 'selective' state value. Only the changes to this derived 'selective' state value determine whether a rebuild of the widget is triggered. In order for changes to be detected correctly, the derived 'selective' state value must have value semantics.
With a SnapshotToPropsMapper function usually a props parameter for a WidgetFromPropsBuilder function is created.
typedefWidgetFromPropsBuilder<P> = WidgetFunction({
Key? key,
required P props,
});
A WidgetFromPropsBuilder is a Function that builds a new widget from the properties of the passed props parameter. That is, the props parameter must contain all the properties necessary for building the widget.
Many widgets have callback properties of type Function. The Function type has no value semantics (each function is unique), this also applies to anonymous functions, which are often used as values for widget callback properties.
If value semantics are needed, Callable can be used for callback properties in the derived 'selective' state values instead of anonymous functions.
abstractclassCallable<T> {
T call();
}
abstractclassCallable1<T, V> {
T call(V value);
}
abstractclassCallable2<T, V1, V2> {
T call(V1 value1, V2 value2);
}
If the signatures of a widget callback property's function and the call method of a callable match, then the callable is assignment-compatible with the widget callback property, e.g.:
In the pubspec.yaml add dependencies on the package 'reduced' and on the package of an implementation of the 'reduced' facade for a state management framework, e.g. 'reduced_bloc'.
In addition to the basic features, state management frameworks also offer these advanced features:
Register a state for management.
Trigger a rebuild on widgets selectively after a state change.
Set up a new scope for state management.
A neutral facade has also been developed for this features in the form of the registerState function and the ReducedProvider, ReducedConsumer and ReducedScope widget classes. Since the features differ for the concrete frameworks, the signatures of the function and the widget constructors are also different, so these function and classes were not included in the 'reduced' facade, but are part of the additional API of the implementations of the 'reduced' facade.
1. Register a state for management.
voidregisterState(S initialValue);
classReducedProvider<S> extendsStatelesswidget{
ReducedProvider({
requiredthis.initialState,
requiredthis.child,
}) ...
final S initialState,
finalWidget child,
...
}
2. Trigger a rebuild on widgets selectively after a state change.