mosaic-client/dev.catbit.mosaic.client.ui.sdui.foundation.data_holder/ScreenDataHolder

ScreenDataHolder

Screen-scoped, in-memory data store — same flat/segmented shape as ApplicationDataHolder, but one fresh instance per screen, discarded when the screen leaves the back stack. Backs the server DSL's screenPlainData()/screenSegmentedData(segmentId) data sources, plus the read-only screenNavigationData() for arguments the screen was navigated to with. Reached in event execution directly as EventRunningScope.screenDataHolder — there's no get<ScreenDataHolder>() Koin lookup, since a new instance is created per screen rather than being a single app-wide binding.

Inheritors

DefaultScreenDataHolder

MosaicScreenStateHolder

Functions

addPlainData

abstract fun addPlainData(data: Any?, dataId: String)

Writes data under dataId in this screen's flat store, overwriting any existing value. The mechanism behind UpdateData targeting screenPlainData().

addSegmentedData

abstract fun addSegmentedData(data: Any?, segmentId: String, dataId: String)

Writes data under dataId within this screen's segmentId namespace, overwriting any existing value. The mechanism behind UpdateData targeting screenSegmentedData(segmentId).

getAllNavigationData

abstract fun getAllNavigationData(): Map<String, Any>

Every navigation argument this screen was opened with.

getAllPlainData

abstract fun getAllPlainData(): Map<String, Any?>

Every flat entry currently stored on this screen, keyed by data id.

getAllSegmentedData

abstract fun getAllSegmentedData(segmentId: String): Map<String, Any?>?

Every entry currently stored within segmentId, keyed by data id.

getNavigationData

abstract fun getNavigationData(dataId: String): Any?

Reads the navigation argument dataId this screen was opened with — read-only, there is no add/remove counterpart, since navigation arguments are fixed for the lifetime of a screen instance. The mechanism behind GetData's screenNavigationData() data source.