Feature/navigation3

[Iwillbeagood]

📋 개요

• Navigation Compose에서 Navigation3 라이브러리로 마이그레이션
• 커스텀 네비게이션 시스템 구축 및 LaunchMode 도입

📑 세부 사항

1. Navigation3 마이그레이션 ✅

• Navigation Compose에서 Navigation3로 전환
• NavDisplay와 entryProvider를 사용한 선언적 네비게이션 구현
• 모든 화면에 대한 NavEntry 생성

2. 커스텀 RouteStack 구현 ✅

data class RouteStack(
    val backStack: List<Route> = emptyList(),
) {
    val current: Route? = backStack.lastOrNull()
    val previous: Route? = backStack.dropLast(1).lastOrNull()
}

• Navigation3와 독립적으로 백스택 상태를 관리
• current, previous 프로퍼티로 현재/이전 화면 정보 제공

3. LaunchMode 도입 ✅

enum class LaunchMode {
    STANDARD,   // 항상 새로운 인스턴스 추가
    SINGLE_TOP, // 최상단이면 재사용
    CLEAR_TOP,  // 백스택에서 찾아 위 제거
    CLEAR_ALL   // 백스택 완전 초기화
}

• Android의 launchMode 개념 차용
• 명확하고 유연한 백스택 관리
• clearBackStack 파라미터 제거로 API 단순화

4. AssistedInject 지원 ✅

@HiltViewModel(assistedFactory = RegistryViewModel.Factory::class)
class RegistryViewModel @AssistedInject constructor(
    @Assisted private val groupId: Long?,
    // ...
)

// RegistryNavEntry.kt
entry<SubRoute.Registry> { route ->
    RegistryRoute(
        viewModel = hiltViewModel(
            creationCallback = { factory: RegistryViewModel.Factory ->
                factory.create(route.groupId)
            }
        )
    )
}

## 🔗 링크
- https://developer.android.com/guide/navigation/navigation-3/migration-guide

[Copilot]

Pull request overview

This PR migrates the navigation system from Navigation Compose to Navigation3, introducing a custom backstack management system with LaunchMode support. The migration modernizes the navigation architecture while providing more explicit control over navigation behavior through the introduction of LaunchMode enum values (STANDARD, SINGLE_TOP, CLEAR_TOP, CLEAR_ALL).

Changes:

• Migrated from Navigation Compose to Navigation3 with NavDisplay and entryProvider pattern
• Implemented custom RouteStack data class for managing navigation backstack independently
• Introduced LaunchMode enum for explicit backstack management behavior
• Updated RegistryViewModel to use @AssistedInject for route parameter injection

Reviewed changes

Copilot reviewed 54 out of 54 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
core/navigation/build.gradle.kts	Updated dependencies from navigation-compose to navigation3-runtime and navigation3-ui
core/navigation/src/main/java/com/teambrake/brake/core/navigation/route/Route.kt	Changed Route to extend NavKey interface for Navigation3 compatibility
core/navigation/src/main/java/com/teambrake/brake/core/navigation/route/RouteStack.kt	Implemented custom RouteStack for backstack state management
core/navigation/src/main/java/com/teambrake/brake/core/navigation/route/LaunchMode.kt	Added LaunchMode enum for navigation behavior control
core/navigation/src/main/java/com/teambrake/brake/core/navigation/action/NavigatorAction.kt	Updated all navigation methods to use LaunchMode instead of NavOptions
core/navigation/src/main/java/com/teambrake/brake/core/navigation/provider/NavigatorProvider.kt	Simplified interface to return Route instead of String
presentation/main/src/main/java/com/teambrake/brake/presentation/main/MainViewModel.kt	Centralized navigation logic with custom RouteStack management
presentation/main/src/main/java/com/teambrake/brake/presentation/main/MainActivity.kt	Restructured initialization flow to work with Navigation3
presentation/main/src/main/java/com/teambrake/brake/presentation/main/MainScreen.kt	Updated to use RouteStack instead of Navigator
presentation/main/src/main/java/com/teambrake/brake/presentation/main/navigation/MainNavHost.kt	Replaced NavHost with NavDisplay and entryProvider pattern
presentation/main/src/main/java/com/teambrake/brake/presentation/main/navigation/MainNavigator.kt	Removed old MainNavigator class (logic moved to MainViewModel)
presentation//navigation/.kt	Removed all old navigation files using NavGraphBuilder
presentation//navEntry/.kt	Added new navEntry files using EntryProviderScope
presentation/*/Screen.kt	Updated hiltViewModel imports to androidx.hilt.lifecycle.viewmodel.compose
presentation/home/src/main/java/com/teambrake/brake/presentation/registry/RegistryViewModel.kt	Converted to use @AssistedInject with Factory pattern
presentation/main/src/main/AndroidManifest.xml	Added transparent system bar theme
presentation/main/src/main/res/values/themes.xml	Created TransparentSystemBar theme
gradle/libs.versions.toml	Added Navigation3 dependencies and updated targetSdk to 36
build-logic/src/main/kotlin/brake.android.feature.gradle.kts	Removed navigation-compose dependencies
.github/git-commit-instructions.md	Added commit message guidelines (unrelated to navigation migration)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The targetSdk has been updated from 35 to 36. Android 15 (API 36) includes significant behavior changes and new restrictions. Ensure that the app has been tested against API 36 requirements, including new runtime permissions, foreground service restrictions, and other breaking changes documented in the Android 15 behavior changes guide. This change could introduce runtime issues if not properly validated.

Suggested change

	targetSdk = "36"
	targetSdk = "35"

[Copilot]

This file appears to be unrelated to the Navigation3 migration described in the PR. It's a commit message guideline document. Consider whether this should be included in this PR or moved to a separate documentation update PR to keep changes focused and easier to review.

[Copilot]

The RouteStack constructor that takes a single Route parameter wraps it in a list. However, the primary constructor initializes backStack with an empty list by default. While this works correctly, consider adding validation to prevent creating a RouteStack with an empty backStack after initialization, as an empty backStack could lead to null current and previous values, which might cause unexpected behavior in navigation logic.

[Copilot]

The CLEAR_TOP implementation may have an issue with route equality. Since SubRoute.Registry is a data class with a nullable groupId parameter, two Registry instances with different groupId values will not be equal (e.g., Registry(groupId=1) != Registry(groupId=2)). This means CLEAR_TOP won't work as expected when navigating to a Registry route that already exists in the backstack with a different groupId. Consider whether this is the intended behavior, or if you need custom equality logic for routes with parameters.

[TaewoongR]

Nav3 적용 후 발생한 문제

1. 스플래시 화면이 Application 단위가 아닌 Activity 구성에서 실행됨
2. 네비게이션 백스택 초기화 후 로그인 화면으로 이동 시, 이전의 로딩 상태가 유지되어 로딩 중 화면이 나타남

해결 방법

1. Activity 스플래시 화면 구성 적용
2. 로그인 화면에서 다음 화면으로 이동하기 직전에 해당 화면 상태 초기화