json_cache 0.2.0 json_cache: ^0.2.0 copied to clipboard
An object-oriented package for caching user data locally in json; a combinable layer on top of local storage packages that unifies them as an elegant caching API.
json_cache #
Contents #
Overview #
Cache is a hardware or software component that stores data so that future requests for that data can be served faster; the data stored in a cache might be the result of an earlier computation or a copy of data stored elsewhere.
Json Cache is an object-oriented package to cache user data locally in json. It can also be thought of as a layer on top of Flutter's local storage packages like sharable_preferences and local storage that unifies them as an elegant caching API.
Why Json?
- Because most of the local storage packages available for Flutter applications use json as the data format.
- There is a one-to-one relationship between Dart's built-in type
Map<String, dynamic>
and json, which makes encoding/decoding data in json a trivial task.
Getting Started #
This package gives developers great flexibility by providing a set of classes that can be selected and grouped in various combinations to meet specific cache requirements.
JsonCache
is the core interface of this package and represents the concept of
cached data. It is defined as:
/// Represents data cached in json.
abstract class JsonCache {
/// Frees up storage space.
Future<void> clear();
/// It either updates the data found at [key] with [value] or, if there is no
/// previous data at [key], creates a new cache row at [key] with [value].
///
/// **Note**: [value] must be json encodable.
Future<void> refresh(String key, Map<String, dynamic> value);
/// Removes data from cache at [key].
Future<void> remove(String key);
/// Retrieves the data value at [key] or null if a cache miss occurs.
Future<Map<String, dynamic>?> value(String key);
}
It is reasonable to consider each cache entry (a key/data pair) as a group of related data. Thus, it is expected to cache data into groups, where a key represents the name of a single data group. For example:
'profile': {'name': 'John Doe', 'email': 'johndoe@email.com', 'accountType': 'premium'};
'preferences': {'theme': {'dark': true}, 'notifications':{'enabled': true}}
Above, the profile key is associated with the profile-related data group, while the preferences key is associated with the preferences-related data.
JsonCacheMem #
It is a thread-safe, in-memory implementation of the JsonCache
interface.
Moreover, it encapsulates a secondary cache or "slower level2 cache". Typically,
the secondary cache instance is responsible for the local cache; that is, it is
the cache instance that persists data on the user's device.
JsonCacheMem Usage
Due to the fact that JsonCacheMem
is a decorator, you should always pass
another JsonCache
instance when you instantiates it. For example:
…
final prefs = await SharedPreferences.getInstance();
final JsonCacheMem jsonCache = JsonCacheMem(JsonCachePrefs(prefs));
…
Demo application #
The demo application provides a fully working example, focused on demonstrating the caching API in action. You can take the code in this demo and experiment with it.
To run the demo application:
git clone https://github.com/dartoos-dev/json_cache.git
cd json_cache/example/
flutter run -d chrome
This should launch the demo application on Chrome in debug mode.