You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Rename Session alert opens empty after the first rename #7
The Rename Session alert is only prefilled with the session's current name the first time it opens after launch. When it opens again, for the same session or another one, the field is empty and shows the Name placeholder.
Steps to reproduce
Launch Shepherdr with at least one session.
Right-click the session in the sidebar → Rename…. The field shows the current name.
Rename it, or cancel.
Right-click a session → Rename… again. The field is empty.
Expected
The field always starts with the session's current workspace name, ready to edit.
Impact
Renaming still works: typing a new name and pressing Rename renames the Herdr workspace. But a small edit to a long name means retyping all of it.
The alert's TextField binds to model.renaming?.name (App/MainView.swift). SwiftUI may be reusing the alert's text field across presentations without reading the binding again.
The Rename Group alert uses the same pattern (model.groupPrompt?.name) and may have the same problem; not checked.
What happens
The Rename Session alert is only prefilled with the session's current name the first time it opens after launch. When it opens again, for the same session or another one, the field is empty and shows the
Nameplaceholder.Steps to reproduce
Expected
The field always starts with the session's current workspace name, ready to edit.
Impact
Renaming still works: typing a new name and pressing Rename renames the Herdr workspace. But a small edit to a long name means retyping all of it.
Notes
mainat a09b789 (after Fix a race when renaming a session #3), macOS 26, in a scratch app copy pointed at a disposable Herdr session.TextFieldbinds tomodel.renaming?.name(App/MainView.swift). SwiftUI may be reusing the alert's text field across presentations without reading the binding again.model.groupPrompt?.name) and may have the same problem; not checked.