chore: add AGENTS.md and .agents/ for Codex agent configuration
This commit is contained in:
5 files changed
+834
No files matched your search
@@ -0,0 +1,73 @@
|
||||
---
|
||||
name: legado-compose-migration
|
||||
description: Guide Legado Android UI migration from XML/View/RecyclerView/DialogFragment screens to Jetpack Compose and Material 3, and guide new Compose-first screens using standard Android architecture. Use when creating, migrating, rewriting, reviewing, or planning a Legado screen, Activity, Fragment, dialog, adapter, navigation destination, or settings page, especially when MainActivity navigation, MVI/UDF, StateFlow/SharedFlow, Koin ViewModels, domain/usecase boundaries, edge-to-edge insets, predictive back, or existing Compose component conventions matter.
|
||||
---
|
||||
|
||||
# Legado Compose Migration
|
||||
|
||||
## Overview
|
||||
|
||||
Migrate one UI surface at a time, or create one new Compose destination at a time. Preserve behavior first for migrations; for newly created screens, prefer standard modern Android architecture over mixed legacy patterns. Use the project's existing `MainActivity` navigation, `BaseComposeActivity` compatibility hosts, `*Screen`, `*Contract`, `*ViewModel`, `StateFlow`, `SharedFlow`, Koin, theme, and widget patterns.
|
||||
|
||||
Before editing, inspect the target View implementation if one exists, `MainActivity` navigation when adding a destination, and at least two nearby migrated Compose screens. For concrete project patterns, including current Compose state/performance rules, read `references/project-patterns.md`.
|
||||
|
||||
## Workflow
|
||||
|
||||
1. State assumptions and success criteria.
|
||||
- Name the exact screen or destination being created/migrated.
|
||||
- For migrations, define behavior that must remain unchanged: inputs, result codes, navigation, menu actions, dialogs/sheets, list selection, refresh, persistence, and event bus behavior.
|
||||
- For new screens, define the route owner, UI state, events/effects, domain/usecase boundary, and verification target.
|
||||
- If the target mixes UI and business logic heavily, keep the migration surgical and defer deeper domain cleanup unless needed.
|
||||
|
||||
2. Map the old surface.
|
||||
- For migrations, read the Activity/Fragment, XML layouts, adapters, menu XML, dialogs, result launchers, and ViewModel.
|
||||
- For new screens, read `MainActivity`, nearby route screens, the relevant ViewModel/usecase/repository patterns, and shared UI components.
|
||||
- List UI state, user intents, one-shot effects, and external side effects.
|
||||
- Identify reusable Compose components under `ui/widget/components` before creating new components.
|
||||
|
||||
3. Choose the minimal migration shape.
|
||||
- For new Compose-first screens, add a `MainActivity` navigation destination instead of creating a standalone Activity.
|
||||
- Use `BaseComposeActivity` for full-screen Activity migrations only when a legacy Activity must remain as an entry point.
|
||||
- Keep existing Activity Result APIs, `Intent` extras, permission flows, and Android framework calls in the host/compatibility Activity.
|
||||
- If an unreworked View screen still starts the migrated screen with `Intent`, keep the old Activity only as a compatibility host that parses legacy extras and delegates to the Compose screen or `MainActivity` route boundary.
|
||||
- Put renderable state in `UiState`, user actions in `Intent`, and one-shot navigation/framework work in `Effect`.
|
||||
- For new screens, use standard Android/Compose architecture: UDF/MVI-style state hoisting, lifecycle-aware Flow collection, ViewModel-owned state, repository/usecase boundaries, and UI free of business logic.
|
||||
- Ensure the new screen handles edge-to-edge correctly: use `Scaffold` (which respects `WindowInsets` automatically) or apply `Modifier.windowInsetsPadding(WindowInsets.safeDrawing)` on the outermost container. Do not carry over `fitsSystemWindows` / manual padding patterns from XML.
|
||||
- Use mixed legacy patterns only as an integration boundary for unreworked View screens or existing framework contracts.
|
||||
- Use existing repositories/usecases when they already fit; introduce new domain/usecase classes when a new screen needs clean business boundaries or when a migration would otherwise duplicate or entangle business logic.
|
||||
|
||||
4. Implement by layers.
|
||||
- Create or update `FeatureContract.kt` first for `UiState`, `Intent`, `Effect`, dialog/sheet models, and menu action enums.
|
||||
- Update `FeatureViewModel.kt` to expose `uiState: StateFlow<UiState>` and `effects: SharedFlow<Effect>`, with a single `onIntent(...)` entry point unless the existing feature has a simpler established pattern.
|
||||
- Create `FeatureScreen.kt` as a stateless route-level composable: `state`, callbacks, and `onIntent`.
|
||||
- Wire new Compose destinations through `MainActivity` route handling; update a retained Activity only when legacy `Intent` compatibility is required.
|
||||
- Collect state with `collectAsStateWithLifecycle()` and collect effects in `LaunchedEffect(Unit)` from the route or compatibility host.
|
||||
- Register new ViewModels in `di/appModule.kt` with `viewModelOf(::FeatureViewModel)` unless parameters require `viewModel { ... }`.
|
||||
|
||||
5. Remove only obsolete migration artifacts.
|
||||
- Delete XML layouts, adapters, menu resources, binding fields, and imports only when the migrated screen no longer references them.
|
||||
- Do not refactor unrelated View screens or shared utilities.
|
||||
|
||||
6. Verify.
|
||||
- Prefer the smallest Gradle check that compiles the touched app code, usually `.\gradlew.bat :app:compileAppDebugKotlin`.
|
||||
- If resources, manifests, or XML deletion are involved, run `.\gradlew.bat :app:assembleAppDebug` when feasible.
|
||||
- For behavior-heavy changes, add or update focused tests only where the project already has a practical test seam.
|
||||
|
||||
## Boundaries
|
||||
|
||||
- Keep Compose functions side-effect-light. Use `LaunchedEffect` for collecting effects and use callbacks for user actions.
|
||||
- Do not pass `Activity`, `View`, binding objects, or mutable domain entities deep into composables unless an existing local pattern requires it.
|
||||
- Prefer project theme/components: `LegadoTheme`, `AppScaffold`, `ListScaffold`, `AppAlertDialog`, `AppModalBottomSheet`, `RoundDropdownMenu`, top bar helpers, setting items, cover components, and list utilities.
|
||||
- Prefer `StateFlow`/`SharedFlow` over `LiveData` for newly migrated Compose surfaces.
|
||||
- Annotate `UiState` data classes and UI-facing model wrappers with `@Stable` when they hold collections or entity data passed to composables. Kotlin 2.x strong skipping is on by default, but explicit `@Stable` provides the strongest compiler guarantee and helps document contract boundaries.
|
||||
- When using `FeatureIntent` for MVI user actions, distinguish it from Android `Intent` extras and launch APIs in names, comments, and explanations where both appear.
|
||||
- For new Compose-first screens, do not copy View-era shortcuts such as UI logic in Activity/Fragment, direct binding-like mutable UI state, adapter-owned state, or Activity-context business operations.
|
||||
- Keep one-off Android actions out of `UiState`: navigation, file opening, clipboard, dialogs implemented as Android DialogFragments, result launchers, permission requests, and callbacks that require host context should be `Effect`s handled by `MainActivity` route handling or a compatibility Activity.
|
||||
- Prefer `MainActivity` navigation for new Compose destinations. Treat standalone Activities for migrated screens as legacy entry points only when existing View code still depends on `Intent` navigation.
|
||||
- For edge-to-edge: this project targets SDK 37, so edge-to-edge is enforced on Android 15+. Use Material 3 `Scaffold` insets or `WindowInsets.safeDrawing` / `safeContent` padding; ensure migrated screens draw behind system bars via `Modifier.windowInsetsPadding()` or top-level scaffold padding rather than manual hardcoded offsets. Migrated screens that relied on `fitsSystemWindows` in XML must be updated.
|
||||
- For predictive back: New Compose destinations should work with the predictive back gesture (enabled by default in Navigation 3). When a screen requires back confirmation (unsaved changes, selection mode), use `BackHandler` to intercept and route through `FeatureIntent.BackPressed`.
|
||||
- Keep existing Chinese string resources and localization behavior; add strings to resources when user-facing text is new.
|
||||
|
||||
## Reference
|
||||
|
||||
Read `references/project-patterns.md` when implementing or reviewing a migration. It contains project-specific examples, file placement rules, state/effect conventions, and verification commands.
|
||||
@@ -0,0 +1,194 @@
|
||||
# Legado Compose Migration Project Patterns
|
||||
|
||||
## Existing Shape
|
||||
|
||||
- App module: `app`.
|
||||
- Main source root: `app/src/main/java/io/legado/app`.
|
||||
- UI package: `ui/...`, usually grouped by feature.
|
||||
- Data package: `data/dao`, `data/entities`, `data/repository`.
|
||||
- Domain package: `domain/gateway`, `domain/model`, `domain/repository`, `domain/usecase`.
|
||||
- DI: `di/appModule.kt`, using Koin `singleOf`, `viewModelOf`, and parameterized `viewModel { ... }`.
|
||||
- Main navigation: `ui/main/MainActivity.kt`, using Navigation3 `NavKey`, `rememberNavBackStack`, `entryProvider`, and `NavDisplay`, plus legacy route extras such as `EXTRA_START_ROUTE`.
|
||||
- Base Compose host: `base/BaseComposeActivity.kt`, which wraps `Content()` in `AppTheme`, configures system bars, locale/font, background image, and LiveBus recreation events.
|
||||
- Compose dependencies are already enabled in `app/build.gradle.kts`; do not add new UI libraries unless the target screen truly requires one.
|
||||
- `kotlinx.collections.immutable` is available for Compose-facing screen state. Prefer `ImmutableList`, `ImmutableSet`, and `ImmutableMap` at `UiState` boundaries when collection state is passed to composables and changes often.
|
||||
|
||||
## Files to Inspect Before Migrating
|
||||
|
||||
Inspect these as local examples, not as APIs to copy blindly:
|
||||
|
||||
- `ui/book/info/BookInfoActivity.kt`
|
||||
- `ui/book/info/BookInfoContract.kt`
|
||||
- `ui/book/info/BookInfoViewModel.kt`
|
||||
- `ui/book/info/BookInfoScreen.kt`
|
||||
- `ui/book/search/SearchContract.kt`
|
||||
- `ui/book/search/SearchViewModel.kt`
|
||||
- `ui/book/search/SearchScreen.kt`
|
||||
- `ui/main/MainActivity.kt`
|
||||
- `ui/main/MainScreen.kt`
|
||||
- `ui/widget/components/AppScaffold.kt`
|
||||
- `ui/widget/components/list/ListScaffold.kt`
|
||||
- `ui/theme/LegadoTheme.kt`
|
||||
- `ui/theme/AppTheme.kt`
|
||||
|
||||
## Recommended Feature Layout
|
||||
|
||||
For a migrated feature, prefer colocated files:
|
||||
|
||||
```text
|
||||
ui/<area>/<feature>/
|
||||
FeatureActivity.kt # only for legacy Intent compatibility or full-screen migration host
|
||||
FeatureContract.kt
|
||||
FeatureViewModel.kt
|
||||
FeatureScreen.kt
|
||||
FeatureSheets.kt # only if sheets are substantial
|
||||
FeatureDialogs.kt # only if dialogs are substantial
|
||||
```
|
||||
|
||||
Use the smallest set of files. Do not split files just to match this shape.
|
||||
|
||||
## MVI and UDF Rules
|
||||
|
||||
Use this shape for behavior-heavy screens:
|
||||
|
||||
```kotlin
|
||||
@Stable
|
||||
data class FeatureUiState(
|
||||
val isLoading: Boolean = false,
|
||||
val items: ImmutableList<Item> = persistentListOf(),
|
||||
val dialog: FeatureDialog? = null,
|
||||
val sheet: FeatureSheet = FeatureSheet.None,
|
||||
)
|
||||
|
||||
sealed interface FeatureIntent {
|
||||
data object BackPressed : FeatureIntent
|
||||
data object Refresh : FeatureIntent
|
||||
data class ItemClick(val id: Long) : FeatureIntent
|
||||
}
|
||||
|
||||
sealed interface FeatureEffect {
|
||||
data object Finish : FeatureEffect
|
||||
data class OpenDetail(val id: Long) : FeatureEffect
|
||||
}
|
||||
```
|
||||
|
||||
ViewModel rules:
|
||||
|
||||
- Keep `_uiState = MutableStateFlow(FeatureUiState())` private and expose `uiState = _uiState.asStateFlow()`.
|
||||
- Keep `_effects = MutableSharedFlow<FeatureEffect>(extraBufferCapacity = 8)` private and expose `effects = _effects.asSharedFlow()`.
|
||||
- Prefer `fun onIntent(intent: FeatureIntent)` as the UI entry point.
|
||||
- Treat `FeatureIntent` as an MVI/user-action type. When Android `Intent` launch/extras are also involved, name variables and explanations clearly enough that the two concepts are not confused.
|
||||
- Use `_uiState.update { it.copy(...) }` for state changes.
|
||||
- Emit one-shot work through effects, not booleans in state.
|
||||
- Keep cached current entities private in the ViewModel when existing project behavior needs mutation or incremental sync, but publish immutable render state.
|
||||
- Annotate `UiState` data classes with `@Stable` to give the Compose compiler the strongest stability guarantee. This is especially important when `UiState` fields include collections or entity types that come from non-Compose modules.
|
||||
- For collection-heavy `UiState`, convert DAO/repository `List`/`Set`/`Map` values to `kotlinx.collections.immutable` at the ViewModel/UI-state boundary with `toImmutableList()`, `toImmutableSet()`, or `toImmutableMap()`. Do not force repository, DAO, or domain APIs to use persistent collections unless the domain contract truly benefits.
|
||||
- Keep internal flow pipelines free to use normal Kotlin collections for sorting, grouping, and persistence work; the immutable collection rule is primarily for values exposed to Compose.
|
||||
- Use existing `BaseViewModel.execute { ... }.onSuccess { ... }.onError { ... }` when the surrounding ViewModel already uses that pattern.
|
||||
|
||||
Activity rules:
|
||||
|
||||
- Prefer `MainActivity` as the owner of Compose-first navigation. Add a Navigation3 route/key and `entryProvider` entry there for new destinations.
|
||||
- Extend `BaseComposeActivity` for migrated Activity screens only when a standalone Activity remains necessary.
|
||||
- Keep a legacy Activity for a migrated screen only when unreworked View code still calls it through `Intent`; in that case, make the Activity a thin compatibility host that translates extras/results and delegates to Compose state/effects.
|
||||
- Keep Activity Result launchers, file openers, clipboard, permission APIs, Android DialogFragments, and framework navigation in the Activity.
|
||||
- In `Content()`, collect state with `collectAsStateWithLifecycle().value`.
|
||||
- Collect effects in `LaunchedEffect(Unit) { viewModel.effects.collectLatest { ... } }`.
|
||||
- Pass only `state` and callbacks into the screen.
|
||||
- Edge-to-edge: Since target SDK ≥ 35, edge-to-edge is enforced. In `BaseComposeActivity`, `enableEdgeToEdge()` is called before `setContent`. Ensure screen-level composables apply `Modifier.windowInsetsPadding(WindowInsets.safeDrawing)` on the outermost non-scaffold container, or rely on Material 3 `Scaffold` (which handles `WindowInsets` automatically). Do not use manual `statusBarsPadding()` / `navigationBarsPadding()` on top of scaffold-level insets — double-padding is a common pitfall.
|
||||
|
||||
Navigation rules:
|
||||
|
||||
- For new Compose-first destinations, add the route to `MainActivity` instead of adding a new Activity.
|
||||
- Follow `MainActivity`'s current route style: serializable `NavKey` routes for in-process navigation and launcher `Intent` helper methods only when external or legacy callers need a stable entry point.
|
||||
- Keep legacy extra names stable when replacing an old Activity entry point.
|
||||
- When a compatibility Activity is retained, let it translate old `Intent` inputs/results; do not make it the source of truth for navigation or business behavior.
|
||||
- Predictive back: Navigation 3 enables predictive back by default on Android 14+. New composable destinations work with it automatically. When a screen needs back confirmation (unsaved changes, selection mode, add-to-shelf prompt), use `BackHandler(enabled = ...) { onIntent(FeatureIntent.BackPressed) }` to intercept and let the ViewModel decide — don't bypass ViewModel back logic.
|
||||
|
||||
Screen rules:
|
||||
|
||||
- Make `FeatureScreen(state, onIntent, ...)` stateless for business state.
|
||||
- Use `remember` and `rememberSaveable` only for local UI affordances such as menu expansion, scroll state, transient animation state, and text field drafts when committing through an intent.
|
||||
- Use `rememberSaveable` for user-driven transient targets that should survive recreation, such as a delete-confirmation item ID or URL. Store only the stable ID in saved state and resolve the current entity from `UiState`.
|
||||
- Use `BackHandler` to route back actions through `FeatureIntent.BackPressed` when ViewModel decisions matter.
|
||||
- Keep expensive derived values in `remember(key)` or ViewModel state when they depend on repository data.
|
||||
- Prefer `LazyColumn`, `LazyRow`, stable keys, and existing fast-scroller/list components for adapter migrations. For heterogeneous lazy lists or grids, provide `contentType` in addition to `key`.
|
||||
- In long-lived `LaunchedEffect` collectors, wrap changing callbacks, `Context`-dependent operations, or lambdas from parents with `rememberUpdatedState` when the effect should not restart.
|
||||
- Hoist state only to the lowest common owner that reads and writes it. Move branch-only ViewModel lookup and Flow collection into the branch or a small child composable instead of collecting at a high-level route.
|
||||
- Avoid UI-state feedback loops such as `LaunchedEffect(uiState.items) { viewModel.pruneSelection(...) }`. Prefer deriving consistency inside the ViewModel with `combine(...)`, or reduce the state as part of the flow that produces the data.
|
||||
|
||||
## Current Compose Performance Notes
|
||||
|
||||
- Kotlin 2.x + Compose compiler plugin (`org.jetbrains.kotlin.plugin.compose`) enables **strong skipping by default**. This means composable functions with unstable parameters CAN still be skipped if their arguments are equal by `equals()`. However, ordinary Kotlin `List`, `Set`, and `Map` are still **unstable types** — passing them as parameters prevents the compiler from inferring stability, so changing a list reference still triggers recomposition of callers even with strong skipping.
|
||||
- Use `@Stable` on `UiState` data classes and UI model wrappers to give the Compose compiler the strongest stability guarantee. `@Stable` tells the compiler: "if `equals()` says two instances are the same, the UI hasn't changed." This is critical for data classes holding collections.
|
||||
- Use `kotlinx.collections.immutable` (`ImmutableList`, `ImmutableSet`, `ImmutableMap`) for render state that crosses into Compose. These are recognized as stable by the Compose compiler. Do not mechanically replace every temporary collection, Room query result, or internal mutable accumulator.
|
||||
- If data entities come from modules where the Compose compiler plugin is not applied, consider a `@Stable` UI model wrapper when the entity is passed deeply through composables and causes measurable recomposition cost.
|
||||
- Treat `SnapshotStateList` / `SnapshotStateMap` as UI-owned mutable state, not as a default ViewModel `UiState` transport type.
|
||||
|
||||
## Clean Architecture Boundaries
|
||||
|
||||
This project is mid-migration, so use Clean Architecture pragmatically. For newly created screens, default to standard modern Android architecture and avoid mixed legacy patterns unless they are needed to interoperate with View screens that have not been rewritten.
|
||||
|
||||
- For new screens, keep UI, presentation, domain, and data boundaries explicit: Compose renders state, ViewModel owns state and intent handling, usecases hold reusable business actions, repositories mediate data access.
|
||||
- For new screens, do not place business rules in Activity/Fragment or composables.
|
||||
- For new screens, do not read DAOs directly from UI/presentation unless the project already has no reasonable repository/usecase boundary and adding one would be disproportionate.
|
||||
- For migrations, use existing DAOs/repositories directly if the old ViewModel already does and the migration is UI-only.
|
||||
- Prefer existing `domain/usecase` classes for reusable business actions such as cache, delete, group update, startup maintenance, reading progress, and WebDAV flows.
|
||||
- Add a usecase when a new screen has meaningful business rules, when logic would otherwise be duplicated across features, or when a UI migration needs to extract meaningful business rules from an Activity/adapter.
|
||||
- Keep UI-only formatting and Compose layout decisions out of domain.
|
||||
- Keep entity-to-display mapping near the UI or ViewModel unless it is reused business language.
|
||||
|
||||
## Compose Components and Theme
|
||||
|
||||
Prefer project components before raw Material widgets:
|
||||
|
||||
- Scaffold/top bars: `AppScaffold`, `GlassTopAppBar...`, `DynamicTopAppBar`, `TopBarActionButton`, `TopBarNavigationButton`.
|
||||
- Lists: `ListScaffold`, `TopFloatingStickyItem`, `VerticalFastScroller`, `SelectionBottomBar`.
|
||||
- Dialog/sheet: `AppAlertDialog`, `AppModalBottomSheet`, `OptionSheet`, text list input components.
|
||||
- Settings: `ClickableSettingItem`, `SwitchSettingItem`, `SliderSettingItem`, `ListSettingItem`, `SettingCard`.
|
||||
- Buttons/chips: `AppIconButton`, `SmallIconButton`, `SmallTextButton`, `ToggleChip`, `AlertButton`.
|
||||
- Covers/images: `CoilBookCover`, `BookshelfCover`, `buildCoverImageRequest`; use Coil for Compose image loading.
|
||||
- Theme: `LegadoTheme.colorScheme`, `LegadoTheme.typography`, `ThemeResolver`, `ProvideThemeOverride` where existing feature behavior needs theme override.
|
||||
|
||||
Avoid introducing a second visual system. If a raw Material 3 component is used, style it from `LegadoTheme`.
|
||||
|
||||
## Migration Checklist
|
||||
|
||||
Before editing:
|
||||
|
||||
- Identify old XML layouts, ViewBinding fields, adapters, decorations, menu XML, dialogs, and result contracts.
|
||||
- Capture behavior: empty/loading/error states, refresh, search, sort, selection, long click, swipe, menu actions, back behavior, result codes, events, and persisted preferences.
|
||||
- Decide whether the task is UI-only or needs domain extraction.
|
||||
- For new screens, explicitly decide the presentation/domain/data boundary before coding; do not default to legacy mixed architecture.
|
||||
|
||||
During editing:
|
||||
|
||||
- Create/update `Contract`, then `ViewModel`, then `Screen`, then `MainActivity` route or compatibility host.
|
||||
- For new Compose destinations, wire navigation through `MainActivity` unless a legacy `Intent` caller must remain supported.
|
||||
- When retaining an Activity for compatibility, keep it small: parse legacy extras, collect effects, bridge result codes, and avoid placing feature business logic there.
|
||||
- Verify edge-to-edge: ensure the screen draws edge-to-edge without overlapping system bars. Use `Scaffold` or `Modifier.windowInsetsPadding(WindowInsets.safeDrawing)`. Remove any `fitsSystemWindows`-based margin hacks from the old layout.
|
||||
- Reuse existing string resources and add new resources for new user-facing text.
|
||||
- Register the ViewModel in `di/appModule.kt`.
|
||||
- Remove only resources made obsolete by this migration.
|
||||
- Keep existing public intent extra names and result codes unless explicitly changing an API.
|
||||
|
||||
Verification:
|
||||
|
||||
- Run `.\gradlew.bat :app:compileAppDebugKotlin` for Kotlin-only changes.
|
||||
- Run `.\gradlew.bat :app:assembleAppDebug` when resources, manifests, XML deletion, or generated bindings are affected.
|
||||
- If a screen uses Room queries or migration-sensitive repositories, run the relevant existing Android/unit tests if practical.
|
||||
- For manual verification, open the migrated screen and compare core flows against the old behavior list.
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
- Do not put navigation or Activity launchers inside composables.
|
||||
- Do not store one-time navigation as nullable fields in `UiState` unless the existing local pattern already does; prefer `SharedFlow` effects.
|
||||
- Do not keep adapter selection state split between old adapter and new Compose state.
|
||||
- Do not delete XML/menu resources until all references and generated binding imports are gone.
|
||||
- Do not add speculative domain layers for a single migrated screen.
|
||||
- Do not use mixed architecture for new screens unless compatibility with unreworked View UI requires it.
|
||||
- Do not make a migrated screen's retained Activity the primary navigation model when `MainActivity` can own the Compose destination.
|
||||
- Do not bypass `BaseComposeActivity` unless the screen must remain inside a Fragment or legacy host.
|
||||
- Do not replace existing event bus or service interactions as part of a UI migration unless required for correctness.
|
||||
- Do not forget edge-to-edge: XML `fitsSystemWindows` does not carry over to Compose. Rely on `Scaffold` or `Modifier.windowInsetsPadding()` instead.
|
||||
- Do not forget `@Stable` on `UiState` data classes — missing annotations cause unnecessary recomposition, especially when state contains collections.
|
||||
Reference in new issue
Block a user