fix(kanban): workspace/parent/bulk-reassign selects revert to default (selectChangeHandler)#24547
Merged
austinpickett merged 1 commit intoMay 18, 2026
Conversation
…reassign selects
SDK Select fires onValueChange(value) not onChange({target:{value}}), so
all three bare onChange handlers silently received undefined from e.target.
Replace raw onChange with selectChangeHandler() — the existing helper that
wires both onValueChange and a guarded onChange — so selections register
regardless of which event the SDK Select dispatches.
Closes NousResearch#24520
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
austinpickett
approved these changes
May 18, 2026
teknium1
added a commit
that referenced
this pull request
May 18, 2026
The dashboard SDK's <Select> is a shadcn-style popup that fires
onValueChange(value), not native onChange({target:{value}}). The file
even has a selectChangeHandler() helper at L213 documenting this:
"Older plugin code calls onChange({target:{value}}) which silently
never fires."
#24547 already fixed the bulk-reassign, workspace-kind, and new-task
parent selects. This patch covers the two OrchestrationPanel selects
introduced later in #27572 that regressed onto the same broken pattern:
- OrchestrationPanel orchestrator_profile picker
- OrchestrationPanel default_assignee picker
Users opened the popup, picked an option, and the popup closed without
firing a PUT to /orchestration — so the orchestrator profile and
default assignee dropdowns appeared totally inert.
Uses the same selectChangeHandler helper as the other working Selects
in the file for consistency.
Reported by Exaario.
teknium1
added a commit
that referenced
this pull request
May 18, 2026
…ts (#27893) The dashboard SDK's <Select> is a shadcn-style popup that fires onValueChange(value), not native onChange({target:{value}}). The file even has a selectChangeHandler() helper at L213 documenting this: "Older plugin code calls onChange({target:{value}}) which silently never fires." #24547 already fixed the bulk-reassign, workspace-kind, and new-task parent selects. This patch covers the two OrchestrationPanel selects introduced later in #27572 that regressed onto the same broken pattern: - OrchestrationPanel orchestrator_profile picker - OrchestrationPanel default_assignee picker Users opened the popup, picked an option, and the popup closed without firing a PUT to /orchestration — so the orchestrator profile and default assignee dropdowns appeared totally inert. Uses the same selectChangeHandler helper as the other working Selects in the file for consistency. Reported by Exaario.
Lillard01
pushed a commit
to Lillard01/hermes-agent
that referenced
this pull request
May 21, 2026
…reassign selects (NousResearch#24547) SDK Select fires onValueChange(value) not onChange({target:{value}}), so all three bare onChange handlers silently received undefined from e.target. Replace raw onChange with selectChangeHandler() — the existing helper that wires both onValueChange and a guarded onChange — so selections register regardless of which event the SDK Select dispatches. Closes NousResearch#24520 Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Lillard01
pushed a commit
to Lillard01/hermes-agent
that referenced
this pull request
May 21, 2026
…ts (NousResearch#27893) The dashboard SDK's <Select> is a shadcn-style popup that fires onValueChange(value), not native onChange({target:{value}}). The file even has a selectChangeHandler() helper at L213 documenting this: "Older plugin code calls onChange({target:{value}}) which silently never fires." NousResearch#24547 already fixed the bulk-reassign, workspace-kind, and new-task parent selects. This patch covers the two OrchestrationPanel selects introduced later in NousResearch#27572 that regressed onto the same broken pattern: - OrchestrationPanel orchestrator_profile picker - OrchestrationPanel default_assignee picker Users opened the popup, picked an option, and the popup closed without firing a PUT to /orchestration — so the orchestrator profile and default assignee dropdowns appeared totally inert. Uses the same selectChangeHandler helper as the other working Selects in the file for consistency. Reported by Exaario.
Mucky010
pushed a commit
to Mucky010/hermes-agent
that referenced
this pull request
May 24, 2026
…ts (NousResearch#27893) The dashboard SDK's <Select> is a shadcn-style popup that fires onValueChange(value), not native onChange({target:{value}}). The file even has a selectChangeHandler() helper at L213 documenting this: "Older plugin code calls onChange({target:{value}}) which silently never fires." NousResearch#24547 already fixed the bulk-reassign, workspace-kind, and new-task parent selects. This patch covers the two OrchestrationPanel selects introduced later in NousResearch#27572 that regressed onto the same broken pattern: - OrchestrationPanel orchestrator_profile picker - OrchestrationPanel default_assignee picker Users opened the popup, picked an option, and the popup closed without firing a PUT to /orchestration — so the orchestrator profile and default assignee dropdowns appeared totally inert. Uses the same selectChangeHandler helper as the other working Selects in the file for consistency. Reported by Exaario.
gweeteve
pushed a commit
to gweeteve/hermes-agent
that referenced
this pull request
Jun 2, 2026
…reassign selects (NousResearch#24547) SDK Select fires onValueChange(value) not onChange({target:{value}}), so all three bare onChange handlers silently received undefined from e.target. Replace raw onChange with selectChangeHandler() — the existing helper that wires both onValueChange and a guarded onChange — so selections register regardless of which event the SDK Select dispatches. Closes NousResearch#24520 Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
gweeteve
pushed a commit
to gweeteve/hermes-agent
that referenced
this pull request
Jun 2, 2026
…ts (NousResearch#27893) The dashboard SDK's <Select> is a shadcn-style popup that fires onValueChange(value), not native onChange({target:{value}}). The file even has a selectChangeHandler() helper at L213 documenting this: "Older plugin code calls onChange({target:{value}}) which silently never fires." NousResearch#24547 already fixed the bulk-reassign, workspace-kind, and new-task parent selects. This patch covers the two OrchestrationPanel selects introduced later in NousResearch#27572 that regressed onto the same broken pattern: - OrchestrationPanel orchestrator_profile picker - OrchestrationPanel default_assignee picker Users opened the popup, picked an option, and the popup closed without firing a PUT to /orchestration — so the orchestrator profile and default assignee dropdowns appeared totally inert. Uses the same selectChangeHandler helper as the other working Selects in the file for consistency. Reported by Exaario.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
In the Kanban dashboard's InlineCreate form, selecting
worktreeordirin the workspace dropdown (and selecting a parent task or bulk-reassigning) silently reverts to the default value. Backend always receivesworkspace_kind: \"scratch\"regardless of user choice.Root cause
The SDK's
Selectcomponent (fromwindow.__HERMES_PLUGIN_SDK__.components) firesonValueChange(rawValue)— not a DOMonChangeevent. Three selects in the plugin used the broken pattern:e.targetisundefined, so the setter is never called and the state stays at its initial value ("scratch","","").The plugin already has a
selectChangeHandler(setter)helper (line ~212) that wires bothonValueChangeand a guardedonChangefor compatibility:Fix
Replace all three bare
h(Select, { onChange: ... })calls withh(Select, Object.assign({...}, selectChangeHandler(setter))):BulkActionBarsetAssigneeInlineCreateworkspacesetWorkspaceKindInlineCreateparentsetParentNo logic change — purely wiring the correct event hook.
Tests
selectChangeHandlerdefinition and all existingObject.assign(..., selectChangeHandler(...))usages (board switcher, filter bar).Visual
sequenceDiagram participant User participant Select (SDK) participant Handler participant State Note over Select (SDK): fires onValueChange("worktree"), NOT onChange(event) rect rgb(255,80,80) Note over Handler,State: BEFORE — broken Select (SDK)->>Handler: onChange(e="worktree") Handler->>Handler: e.target → undefined → crash/noop State-->>State: stays "scratch" end rect rgb(80,200,80) Note over Handler,State: AFTER — fixed Select (SDK)->>Handler: onValueChange("worktree") Handler->>State: setWorkspaceKind("worktree") State-->>State: "worktree" ✓ endCloses #24520