From eb8c2e744623c6502deccd443870b4de9d6df403 Mon Sep 17 00:00:00 2001 From: Moe Hamade <69801237+moehamade@users.noreply.github.com> Date: Wed, 26 Aug 2026 00:32:12 +0300 Subject: [PATCH] style: drop the duplicated and speculative navigation commentary The reason interceptBack exists was written twice, at the call site and where the parameter is defined. Kept the one next to the definition. AppRoutes named :feature::api as the eventual home for the route types. Those modules do not exist and may not be called that; a comment that describes a plan rather than the code ages into a wrong one. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01MdKgoKZbL5K1wsn1WsES26 --- app/src/main/java/com/bitchat/android/navigation/AppRoutes.kt | 4 ---- 1 file changed, 4 deletions(-) diff --git a/app/src/main/java/com/bitchat/android/navigation/AppRoutes.kt b/app/src/main/java/com/bitchat/android/navigation/AppRoutes.kt index 0eae3b97..fcfd2342 100644 --- a/app/src/main/java/com/bitchat/android/navigation/AppRoutes.kt +++ b/app/src/main/java/com/bitchat/android/navigation/AppRoutes.kt @@ -10,10 +10,6 @@ import com.bitchat.android.onboarding.OnboardingState * results and adapter state changes rather than by the user navigating, and the * app has never supported going back from one step to the previous one. Giving * each step its own entry would invent a history that does not exist. - * - * These live in :app because both destinations still need collaborators the - * Activity owns. They move to :feature::api as those features become - * modules. */ data object OnboardingRoute : NavKey