fix: critical navigation bug - users trapped in detail and restore screens

Browse Source

Changed return value from 'return s, nil' to 'return nil, nil' in:
- detail.go (line 116): Back navigation from client details
- restore.go (line 101): Back navigation from restore screen

Root cause: Main model's navigation logic checks if newScreen == nil.
When screens returned (s, nil), the check failed and screen never changed.
Now properly returns (nil, nil) to signal screen change to parent.

Fixes: wg-admin-rfo

...

This commit is contained in:

Calmcacil

2026-01-12 22:27:16 +01:00

parent e7d81674c8

commit 8fb3fe7031

3 changed files with 4 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2

.beads/issues.jsonl

File diff suppressed because one or more lines are too long