James Rich f2e664614f fix(node): navigate up after confirming node removal ... After the user taps Confirm on the remove-node dialog, the screen was left in a dead end showing ghost data. CommonGetNodeDetailsUseCase substitutes a fallback node rather than emitting null, so the UI had no signal to navigate away. Fix: thread an onAfterRemove callback through requestRemoveNode → handleNodeMenuAction → handleNodeAction, so onNavigateUp is invoked inside the onConfirm lambda immediately after removeNode() is launched. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>		2026-04-20 07:26:15 -05:00
..
connections	fix(ui): finish accessibility roles and action labels for clickable surfaces (#5170)	2026-04-17 17:33:38 +00:00
firmware	refactor: use injected ioDispatcher and ApplicationCoroutineScope (#5167)	2026-04-17 16:18:45 +00:00
intro	test: migrate Compose UI tests from androidTest to commonTest (#5091)	2026-04-12 20:20:00 +00:00
map	feat(core/ui): add safeLaunch, UiState, KMP permissions, and CMP lifecycle modernization (#5118)	2026-04-14 00:45:34 +00:00
messaging	fix(ui): finish accessibility roles and action labels for clickable surfaces (#5170)	2026-04-17 17:33:38 +00:00
node	fix(node): navigate up after confirming node removal	2026-04-20 07:26:15 -05:00
settings	feat(mqtt): adopt mqttastic-client-kmp 0.2.0 — disconnect reasons + Test Connection (#5181)	2026-04-17 21:33:55 -05:00
widget	fix(widget): drive updates via debounced state observer (#5185)	2026-04-18 04:11:32 +00:00
wifi-provision	fix(ui): finish accessibility roles and action labels for clickable surfaces (#5170)	2026-04-17 17:33:38 +00:00