revert(map): back out per-waypoint DM/channel recipient picker (#6218) - #6284
Conversation
…6218)" This reverts commit 8f3bf00. Per maintainer discussion, per-waypoint channel/DM routing is a departure from Meshtastic's model where the firmware — not the user — decides where a packet goes. Every packet carries channel/position info, and having users manually direct each waypoint adds significant UI complexity for regular users. The intended behavior is to align with position: the first precision-position channel is the one used, managed by firmware position logic rather than an Android-side picker. Backing this out restores the prior broadcast-only waypoint editor. The underlying BaseMapViewModel.sendWaypoint contactKey plumbing predates this PR and is left intact; only the UI picker and the sort-preference extraction it introduced are reverted. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (16)
💤 Files with no reviewable changes (11)
📝 WalkthroughWalkthroughWaypoint recipient selection and contact-key routing were removed from map editing. Map view models now use simplified waypoint sending and node flows, while platform map wiring, preferences, resources, build configuration, and related tests were updated. ChangesWaypoint and map simplification
Estimated code review effort: 3 (Moderate) | ~25 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Reverts #6218.
Per maintainer discussion, per-waypoint channel/DM routing is a departure from
Meshtastic's model where the firmware — not the user — decides where a packet
goes. Every packet already carries channel/position info, and asking regular users
to manually direct each waypoint adds significant UI complexity for little gain.
The intended behavior is to align waypoints with position handling: the first
precision-position channel is the one used, managed by firmware position logic
rather than an Android-side picker.
This backs out the "Send to" recipient picker added to the waypoint editor and
restores the prior broadcast-only behavior. The underlying
BaseMapViewModel.sendWaypointcontactKeyplumbing predates #6218 and is leftintact — only the UI picker and the sort-preference refactor it introduced are
reverted.
🧹 Chores
EditWaypointDialog"Send to" row +WaypointRecipientPicker) — waypoints broadcast to the primary channel again.UiPrefs.nodeSortOption/NodeSortOption.fromOrdinalextraction that feat(map): send a waypoint as a DM or to a specific channel #6218 introduced solely to feed the picker's node list;
NodeFilterPreferencesreturns to its inline ordinal mapping.waypoint_recipient_broadcast,waypoint_recipient_channel, andwaypoint_send_tostring resources.Testing Performed
8f3bf001— applied with no conflicts; the latertraceroute change (fix: stabilize traceroute map node identity & fix log metric alignment #6270) in
google/MapView.ktis preserved.spotlessApply spotlessCheck detekt assembleDebug test allTests kmpSmokeCompile— all green.Summary by CodeRabbit