core-data/org.meshtastic.core.data.repository

Package-level declarations

Types

class BootloaderOtaQuirksRepositoryImpl(remoteDataSource: BootloaderOtaQuirksRemoteDataSource, localDataSource: BootloaderOtaQuirksLocalDataSource, assetReader: BundledAssetReader, json: Json, dispatchers: CoroutineDispatchers) : BootloaderOtaQuirksRepository

Caches the nRF52 bootloader/OTA quirk catalog from the Meshtastic API (/resource/bootloaderOtaQuirks), seeded from the bundled device_bootloader_ota_quirks.json snapshot so it is never empty offline. Unlike DeviceHardwareRepositoryImpl (which this mirrors for seeding), reconcile carries no TTL of its own — DeviceHardwareRepositoryImpl's own refresher calls it on the same cadence as its catalog refresh, so the two caches age together instead of drifting on separate schedules.

DeviceHardwareRepositoryImpl

class DeviceHardwareRepositoryImpl(remoteDataSource: DeviceHardwareRemoteDataSource, localDataSource: DeviceHardwareLocalDataSource, assetReader: BundledAssetReader, json: Json, deviceLinkRepository: DeviceLinkRepository, bootloaderOtaQuirksRepository: BootloaderOtaQuirksRepository, dispatchers: CoroutineDispatchers) : DeviceHardwareRepository

DeviceLinkRepositoryImpl

class DeviceLinkRepositoryImpl(remoteDataSource: DeviceLinksRemoteDataSource, assetReader: BundledAssetReader, json: Json, localDataSource: DeviceLinkLocalDataSource, dispatchers: CoroutineDispatchers) : DeviceLinkRepository

Caches the resolved device-links catalog from the Meshtastic API (/resource/deviceLinks). The server does all the classification (type/targets/regions), so the client just seeds from a bundled snapshot, refreshes from the network, and filters the cache. Mirrors DeviceHardwareRepositoryImpl's seed → single-flight refresh pattern.

EventFirmwareRepositoryImpl

class EventFirmwareRepositoryImpl(remoteDataSource: EventFirmwareRemoteDataSource, assetReader: BundledAssetReader, json: Json, localDataSource: EventFirmwareEditionLocalDataSource, dispatchers: CoroutineDispatchers) : EventFirmwareRepository

Caches event-firmware display metadata in the DB, seeded from the bundled event_firmware.json snapshot and refreshed from /resource/eventFirmware. DB-backed (not just in-memory) so the snapshot survives across process restarts without waiting on a fresh network round-trip. Mirrors DeviceHardwareRepositoryImpl's seed → single-flight refresh pattern.

FirmwareReleaseRepositoryImpl

open class FirmwareReleaseRepositoryImpl(remoteDataSource: FirmwareReleaseRemoteDataSource, localDataSource: FirmwareReleaseLocalDataSource, assetReader: BundledAssetReader, json: Json, dispatchers: CoroutineDispatchers) : FirmwareReleaseRepository

LocationRepositoryImpl

class LocationRepositoryImpl(context: Application, locationManager: Lazy<LocationManager>, analytics: PlatformAnalytics, dispatchers: CoroutineDispatchers) : LocationRepository

MaintenanceUf2RepositoryImpl

class MaintenanceUf2RepositoryImpl(remoteDataSource: MaintenanceUf2RemoteDataSource, localDataSource: MaintenanceUf2LocalDataSource, assetReader: BundledAssetReader, json: Json) : MaintenanceUf2Repository

Caches the maintenance-UF2 manifest from the Meshtastic API (/resource/maintenanceUf2), seeded from the bundled maintenance_uf2.json snapshot so it is never empty offline — mirrors BootloaderOtaQuirksRepositoryImpl's seed-then-refresh shape exactly, including its "reconcile carries no TTL of its own" contract: DeviceHardwareRepositoryImpl's refresher calls this on the same cadence as its catalog refresh.

MeshLogRepositoryImpl

open class MeshLogRepositoryImpl(dbManager: DatabaseProvider, dispatchers: CoroutineDispatchers, meshLogPrefs: MeshLogPrefs, nodeInfoReadDataSource: NodeInfoReadDataSource) : MeshLogRepository

Repository implementation for managing and retrieving logs from the local database.

NodeRepositoryImpl

class NodeRepositoryImpl(processLifecycle: Lifecycle, nodeInfoReadDataSource: NodeInfoReadDataSource, nodeInfoWriteDataSource: NodeInfoWriteDataSource, dispatchers: CoroutineDispatchers, localStatsDataSource: LocalStatsDataSource) : NodeRepository

Repository for managing node-related data, including hardware info, node database, and identity.

PacketRepositoryImpl

class PacketRepositoryImpl(dbManager: DatabaseProvider, dispatchers: CoroutineDispatchers) : PacketRepository

QuickChatActionRepositoryImpl

class QuickChatActionRepositoryImpl(dbManager: DatabaseProvider, dispatchers: CoroutineDispatchers) : QuickChatActionRepository

RadioConfigRepositoryImpl

open class RadioConfigRepositoryImpl(nodeDB: NodeRepository, channelSetDataSource: SwitchingChannelSetDataSource, localConfigDataSource: LocalConfigDataSource, moduleConfigDataSource: ModuleConfigDataSource) : RadioConfigRepository

TracerouteSnapshotRepositoryImpl

class TracerouteSnapshotRepositoryImpl(dbManager: DatabaseProvider, dispatchers: CoroutineDispatchers) : TracerouteSnapshotRepository