Aus öffentlichen Paketdaten erstellte Orientierung.
Stock ist ein Dart-Paket, das für eine effiziente asynchrone Datenladung und -Caching in Flutter-Anwendungen entwickelt wurde. Es vereinfacht die Integration lokaler Datenspeicher – wie Datenbanken oder In-Memory-Caches – mit entfernten Netzwerkanfragen und sorgt für Datenkonsistenz und Leistung. Durch eine einheitliche Schnittstelle ermöglicht Stock Entwicklern sichere Abruf-, Caching- und Aktualisierungsvorgänge für Daten, verringert Boilerplate-Code und behandelt Randfälle wie veraltete Daten oder Netzwerkfehler. Ideal für Apps, die zuverlässigen Offline-Zugriff und Echtzeit-Updates erfordern.
Anwendungsfälle
Datenabruf zuerst offline
API-Antworten zwischenspeichern
Synchronisieren lokaler und remote Daten
Echtzeit-Datenaktualisierungen
Reduzierung redundanten Netzwerkaufrufe
App-Zustand mit zwischengespeicherten Daten verwalten
Hauptmerkmale
Einheitlicher lokaler und Netzwerkdatenzugriff
Automatische Cache-Invalidierung
Unterstützung für asynchrone Datenströme
Eingebaute Wiederholungs- und Fallback-Mechanismen
Leicht und nicht störend
Nahtlose Integration mit bestehenden Datenlagen
Geeignet für
Apps, die eine leistungsstarke Offline-Funktionalität benötigen
Entwickler, die eine vereinfachte Datenverwaltung suchen
Projekte mit häufigen API-Interaktionen
Teams, die wartbare Datenlogik priorisieren
Flutter-Apps, die reaktive Programmiermuster verwenden
Anwendungen, die konsistente Daten über Gerätestatus hinweg erfordern
Hinweise
Erfordert Verständnis von Async/Await-Mustern
Möglicherweise ist zusätzliche Einrichtung für komplexe Cache-Strategien erforderlich
Keine vollständige ORM- oder Datenbanklösung
Am besten geeignet für Lese-intensive Operationen
Eingeschränkter integrierter Support für komplexe Abfragefilterung
Hängt von externen Speicherimplementierungen für Persistenz ab
Original-README
Originaler README-Schnappschuss aus dem verknüpften Quell-Repository. Aktuelle Inhalte finden Sie im Repository.
Stock is a dart package for loading data from both remote and local sources.
It is inspired by the Store Kotlin library.
Its main goal is to prevent excessive calls to the network and disk cache.
By utilizing it, you eliminate the possibility of flooding your network with the same request while, at the same time, adding layers of caching.
Although you can use it without a local source, the greatest benefit comes from combining Stock with a local database such as Floor, Drift, Sqflite, Realm, etc.
Features
Combine local (DB, cache) and network data simply. It provides a data Stream where you can listen and work with your data.
Know the data Stream state. It's useful for displaying errors or loading indicators, for example.
If you are not using a local DB, Stock provides a memory cache, to share and improve upon your app's experience.
Work with your data more safely. If an error is thrown, Stock will catch it and return it into the stream so it can be handled easily.
Overview
A Stock is responsible for managing a particular data request.
It is based on two important classes:
Fetcher: defines how data will be fetched over the network.
SourceOfTruth: defines how local data will be read and written in your local cache. Although Stock can be used without it, we recommend its usage.
Stock uses generic keys as identifiers for data.
A key can be any value object that properly implements toString(), equals() and hashCode().
When you create Stock, it provides you with a bunch of methods in order to access the data.
The most important one is stream(), which provides you with a Stream of your data, which can be used to update your UI or to do a specific action.
The Fetcher is required to fetch new data from the network.
You can create it from a Future or from a Stream.
FutureFetcher is usually used alongside a RestApi, whereas StreamFetcher is used with a Stream source like a Web Socket.
final futureFetcher = Fetcher.ofFuture<String, List<Tweet>>(
(userId) => _api.getUserTweets(userId),
);
final streamFetcher = Fetcher.ofStream<String, List<Tweet>>(
(userId) => _api.getUserTweetsStream(userId),
);
2. Create a Source Of Truth
The SourceOfTruth is used to read and write the remote data in a local cache.
Generally you will implement the SourceOfTruth using a local database. However, if you are not using a local database / cache, the library provides the CachedSourceOfTruth, a source of truth which stores the data in memory.
final sourceOfTruth = SourceOfTruth<String, List<Tweet>>(
reader: (userId) => _database.getUserTweets(userId),
writer: (userId, tweets) => _database.writeUserTweets(userId, tweets),
delete: (userId) => _database.deleteUserTweets(userId), // this is optional
deleteAll: () => _database.deleteAllTweets(), // this is optional
);
In this example, Fetcher type is exactly the SourceOfTruth type. If you need to use multiple types, you can use the mapTo extension.
Note: to the proper operation, when write is invoked with new data, the source of truth has to emit the new value in the reader.
3. Create the Stock
Stock lets you combine the different data sources and get the data.
final stock = Stock<String, List<Tweet>>(
fetcher: fetcher,
sourceOfTruth: sourceOfTruth,
);
Get a data Stream from Stock
You can generate a data Stream using stream().
You need to invoke it with a specific key, and an optional refresh value that tells Stock if a refresh is optional or mandatory.
That returns a data stream of StockResponse, which has 3 possible values:
StockResponseLoading informs that a network request is in progress. It can be useful to display a loading indicator in your UI.
StockResponseData holds the response data. It has a value field which includes an instance of the type returned by Stock.
StockResponseError indicates that an error happened.
When an error happens, Stock does not throw an exception, instead, it wraps it in this class.
It includes an error field that contains the exception thrown by the given origin.
Each StockResponse includes an origin field which specifies where the event is coming from.
Stock provides a couple of methods to get data without using a data stream.
get returns cached data -if it is cached- otherwise will return fresh/network data (updating your caches).
fresh returns fresh data updating your cache
clear purge a particular entry from memory and disk cache
clearAll Purge all entries from memory and disk cache
// Get fresh datafinalList<Tweet> freshTweets = await stock.fresh(key);
// Get the previous cached datafinalList<Tweet> cachedTweets = await stock.get(key);
// Clear key from stockawait stock.clear(key);
// Clear all keys from stockawait stock.clearAll();
Use different types for Fetcher and SourceOfTruth
Sometimes you need to use different entities for Network and DB. For that case Stock provides the StockTypeMapper, a class that transforms one entity into the other.
StockTypeMapper is used in the SourceOfTruth via the method mapToUsingMapper
Sometimes your Source of Truth does not provide you with a real-time data stream.
For example, suppose that you are using shared_preferences to store your data, or you are just catching your data in memory.
For these cases, Stock provides you the CachedSourceOfTruth, a SourceOfTruth that be helpful in these cases.
classSharedPreferencesSourceOfTruthextendsCachedSourceOfTruth<String, String> {
SharedPreferencesSourceOfTruth();
@override@protectedStream<T?> reader(String key) async* {
final prefs = awaitSharedPreferences.getInstance();
// Read data from an non-stream sourcefinal stringValue = prefs.getString(key);
setCachedValue(key, stringValue);
yield* super.reader(key);
}
@override@protectedFuture<void> write(String key, String? value) async {
final prefs = awaitSharedPreferences.getInstance();
await prefs.setString(key, value);
awaitsuper.write(key, value);
}
}
This class can be used with StockTypeMapper to transform your data into an entity.
// The mapper json to transform a string into a User finalStockTypeMapper<String, User> mapper = _createUserMapper();
finalSharedPreferencesSourceOfTruth<String, User> = SharedPreferencesSourceOfTruth()
.mapToUsingMapper(mapper);
Copyright (c) 2022 Xmartlabs SRL.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.