create

expect fun <T> create( storage: Storage<T>, corruptionHandler: ReplaceFileCorruptionHandler<T>? = null, migrations: List<DataMigration<T>> = listOf(), scope: CoroutineScope = CoroutineScope(ioDispatcher() + SupervisorJob())): DataStore<T>(source)

@JvmOverloads

fun <T> create( serializer: Serializer<T>, corruptionHandler: ReplaceFileCorruptionHandler<T>? = null, migrations: List<DataMigration<T>> = listOf(), scope: CoroutineScope = CoroutineScope(Dispatchers.IO + SupervisorJob()), produceFile: () -> File): DataStore<T>(source)

Create an instance of SingleProcessDataStore. Never create more than one instance of DataStore for a given file; doing so can break all DataStore functionality. You should consider managing your DataStore instance as a singleton. If there are multiple DataStores active, DataStore will throw IllegalStateException when reading or updating data. A DataStore is considered active as long as its scope is active.

T is the type DataStore acts on. The type T must be immutable. Mutating a type used in DataStore invalidates any guarantees that DataStore provides and will result in potentially serious, hard-to-catch bugs. We strongly recommend using protocol buffers: https://developers.google.com/protocol-buffers/docs/javatutorial - which provides immutability guarantees, a simple API and efficient serialization.

Return

a new DataStore instance with the provided configuration

Parameters

serializer

Serializer for the type T used with DataStore. The type T must be immutable.

corruptionHandler

The corruptionHandler is invoked if DataStore encounters a CorruptionException when attempting to read data. CorruptionExceptions are thrown by serializers when data can not be de-serialized.

migrations

Migrations are run before any access to data can occur. Migrations must be idempotent.

scope

The scope in which IO operations and transform functions will execute.

produceFile

Function which returns the file that the new DataStore will act on. The function must return the same path every time. No two instances of DataStore should act on the same file at the same time.

@JvmOverloads

actual fun <T> create( storage: Storage<T>, corruptionHandler: ReplaceFileCorruptionHandler<T>?, migrations: List<DataMigration<T>>, scope: CoroutineScope): DataStore<T>(source)

Create an instance of SingleProcessDataStore. Never create more than one instance of DataStore for a given file; doing so can break all DataStore functionality. You should consider managing your DataStore instance as a singleton. If there are multiple DataStores active, DataStore will throw IllegalStateException when reading or updating data. A DataStore is considered active as long as its scope is active.

T is the type DataStore acts on. The type T must be immutable. Mutating a type used in DataStore invalidates any guarantees that DataStore provides and will result in potentially serious, hard-to-catch bugs. We strongly recommend using protocol buffers: https://developers.google.com/protocol-buffers/docs/javatutorial - which provides immutability guarantees, a simple API and efficient serialization.

Return

a new DataStore instance with the provided configuration

Parameters

storage

Storage for the type T used with DataStore. The type T must be immutable.

corruptionHandler

The corruptionHandler is invoked if DataStore encounters a CorruptionException when attempting to read data. CorruptionExceptions are thrown by serializers when data can not be de-serialized.

migrations

Migrations are run before any access to data can occur. Migrations must be idempotent.

scope

The scope in which IO operations and transform functions will execute.

actual fun <T> create( storage: Storage<T>, corruptionHandler: ReplaceFileCorruptionHandler<T>?, migrations: List<DataMigration<T>>, scope: CoroutineScope): DataStore<T>(source)

Create an instance of SingleProcessDataStore. Never create more than one instance of DataStore for a given file; doing so can break all DataStore functionality. You should consider managing your DataStore instance as a singleton. If there are multiple DataStores active, DataStore will throw IllegalStateException when reading or updating data. A DataStore is considered active as long as its scope is active.

T is the type DataStore acts on. The type T must be immutable. Mutating a type used in DataStore invalidates any guarantees that DataStore provides and will result in potentially serious, hard-to-catch bugs. We strongly recommend using protocol buffers: https://developers.google.com/protocol-buffers/docs/javatutorial - which provides immutability guarantees, a simple API and efficient serialization.

Return

a new DataStore instance with the provided configuration

Parameters

storage

Storage for the type T used with DataStore. The type T must be immutable.

corruptionHandler

The corruptionHandler is invoked if DataStore encounters a CorruptionException when attempting to read data. CorruptionExceptions are thrown by serializers when data can not be de-serialized.

migrations

Migrations are run before any access to data can occur. Migrations must be idempotent.

scope

The scope in which IO operations and transform functions will execute.