feat(settings): move Notification Routing into Developer Options#1283
Conversation
Re-parent the Notification Routing panel from the top-level settings menu into the Developer Options sub-menu, keeping the route path and component unchanged. Breadcrumb now reads Settings > Developer Options > Notification Routing. Closes tinyhumansai#1276
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThis PR relocates the "Notification Routing" settings panel from the top-level settings menu to the Developer Options subsection. The menu item is removed from SettingsHome, added to DeveloperOptionsPanel, route definitions are reorganized, and breadcrumb logic is updated to reflect the new hierarchy. ChangesNotification Routing Hierarchy Reorganization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Comment |
… Routing moved to Dev Options) Remove Notification Routing from top-level General section since upstream moved it into Developer Options. Keep grouped section structure.
Summary
SettingsHome.tsx)DeveloperOptionsPanel.tsx)useSettingsNavigation.ts)<Route>declaration next to other Developer Options routes (Settings.tsx)Test plan
useSettingsNavigationbreadcrumbs (notification-routing, notifications, developer-options)Closes #1276
Summary by CodeRabbit