Tags from DevAnalyzer

v1.3.0

2026-02-17T09:03:55Z

refactor: update logging and dependency injection configuration

- Move logging writers to core dependency injection module
- Remove unused logging module and environment parameters from initialization
- Integrate log writer registration into crash reporting lifecycle
- Update exception handling and stack trace formatting in log writers
- Simplify application entry point by removing environment-specific configuration

v1.2.0

2026-02-17T09:04:15Z

feat: Add Clean Build feature to find and delete build folders

This commit introduces a new "Clean Build" feature, allowing users to scan for and delete `build` directories within their projects to free up disk space.

The feature includes a dedicated screen with the following functionalities:
* Browsing for a root project directory (e.g., `AndroidStudioProjects`).
* Scanning the selected directory to identify Gradle projects and their `build` folders.
* Displaying a detailed, hierarchical view of projects and their modules, along with the size of each `build` folder.
* Functionality to select/deselect all, expand/collapse all, and individually select projects or modules for deletion.
* A floating action button to initiate the deletion process, showing the number of selected folders and the total space that will be freed.
* Confirmation and result dialogs to ensure a safe and clear user experience.

### Key Changes:

* **`composeApp/src/jvmMain/kotlin/com/meet/dev/analyzer/presentation/screen/cleanbuild`**: Added a new screen package containing the UI (`CleanBuildScreen.kt`), ViewModel (`CleanBuildViewModel.kt`), UI state (`CleanBuildUiState.kt`), and user intents (`CleanBuildIntent.kt`).
* **`composeApp/src/jvmMain/kotlin/com/meet/dev/analyzer/data`**:
* Created `CleanBuildRepository` and its implementation to handle the logic for scanning projects and deleting folders.
* Defined new data models `ProjectBuildInfo` and `ModuleBuild` for the feature.
* **`composeApp/src/jvmMain/kotlin/com/meet/dev/analyzer/di`**: Updated `RepositoryModule.kt` and `ViewModule.kt` to provide dependencies for the new feature.
* **`composeApp/src/jvmMain/kotlin/com/meet/dev/analyzer/presentation/navigation`**:
* Integrated the "Clean Build" screen into the app's navigation graph (`AppNavigation.kt`, `AppRoute.kt`).
* Added a new "Clean Build" item to the main navigation rail (`NavigationItem.kt`).
* **`composeApp/src/jvmMain/kotlin/com/meet/dev/analyzer/core/utility/Utils.kt`**: Added a `formatElapsedTime` utility function.

v1.1.0

2025-12-01T13:24:46Z

v1.0.0

2025-11-04T12:30:41Z

refactor: Introduce nested navigation graphs and share ViewModels

This commit refactors the navigation structure to use nested navigation graphs, improving organization and state management. It also modifies how ViewModels are scoped to share instances between screens within the same navigation graph, preserving UI state across tabs.

### Key Changes:

* **Nested Navigation Graphs (`AppNavigation.kt`, `AppRoute.kt`):**
* Introduced a `MainGraph` to encapsulate the primary application screens (`ProjectAnalyzer`, `StorageAnalyzer`) and a `SplashGraph` for the initial launch flow (`Splash`, `Onboarding`).
* This groups related destinations, simplifying navigation logic and making the flow more robust.

* **ViewModel Sharing (`ProjectAnalyzerScreen.kt`, `StorageAnalyzerScreen.kt`):**
* `ProjectAnalyzerViewModel` and `StorageAnalyzerViewModel` are now scoped to the `MainGraph`.
* This is achieved by passing the `NavBackStackEntry` of the parent graph (`MainGraph`) to the `koinViewModel` factory.
* As a result, the ViewModels are shared across the composables within the `MainGraph`, preserving the state of each screen when switching between the "Project" and "Storage" tabs.

* **Navigation Logic Cleanup (`AppNavigation.kt`):**
* Removed manual `popUpTo` logic with `findStartDestination()`. The new navigation structure with `launchSingleTop = true` and `restoreState = true` handles this more cleanly.

* **UI Enhancements (`TopAppBar.kt`):**
* The `TopAppBar` now supports an optional back navigation icon, which can be enabled by providing a `navigationOnClick` lambda.