fix!: Ensure data stores persist across configuration changes

[jonnyandrew]

Changes

• Lift in-memory stores out of the composition scope into a new singleton Dagger component.

New public API

Before, you could initialise CRI Orchestrator SDK within the composition like so:

@Composable
fun MyComposable() {
    val criOrchestratorComponent = rememberCriOrchestrator(
        authenticatedHttpClient = httpClient,
        analyticsLogger = analyticsLogger,
        initialConfig = config,
        logger = logger,
    )
}

Now you should initialise the CRI Orchestrator SDK as a singleton in your app using:

// Create one instance of this object
val criOrchestratorSdk = CriOrchestratorSdk.create(
    ...
)

And use this later in your composition:

@Composable
fun MyComposable() {
    val criOrchestratorComponent = rememberCriOrchestrator(
        criOrchestratorSdk = criOrchestratorSdk
    )
}

Context

DCMAW-12575

This change allows some state from the SDK to outlive the composition so that it survives configuration changes.

Evidence of the change

Checklist

• Check against acceptance criteria
• Add automated tests
• Self-review code

[github-actions]

Analytics test report is available to download.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
73.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud