Headcount select stale after reset (#2219)¶
Problem¶
A standard user could add one travel entry (e.g. train or plane), but a second one silently failed to create — the page had to be reloaded before another entry could be added.
Root cause¶
The bug wasn't specific to trains/planes: it was in the shared
headcount-member q-select used by the generic travel-like dynamic form.
That select was keyed only on headcountMemberCount, so calling the form's
reset() after a successful submission didn't force Vue to remount it. The
select was left holding stale internal state, which blocked further
submissions until a full page reload reset it.
What shipped¶
PR #2333, "fix: force re-render of headcount select on reset (#2219)",
merged 2026-08-25 (6bac075da).
frontend/src/components/organisms/module/ModuleForm.vue (+3/-1):
ModuleForm.vue:667— newconst headcountSelectKey = ref(0).ModuleForm.vue:155— the select's:keybinding becomes`${headcountMemberCount}-${headcountSelectKey}`instead ofheadcountMemberCountalone.ModuleForm.vue:1275—reset()incrementsheadcountSelectKey.value, forcing Vue to destroy/remount the select on every reset instead of reusing the stale instance.
No follow-up issues filed.