fix(ui): handle unknown bead statuses gracefully to prevent crashes (Issue 49)#57
Closed
mattwhetton wants to merge 3 commits into
Closed
fix(ui): handle unknown bead statuses gracefully to prevent crashes (Issue 49)#57mattwhetton wants to merge 3 commits into
mattwhetton wants to merge 3 commits into
Conversation
…tatus Skip beads with statuses not in the kanban board columns (e.g., tombstone for soft-deleted items) instead of crashing with undefined.push() error. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add a check before pushing beads to grouped status arrays to prevent TypeError when encountering unknown statuses like "tombstone" for soft-deleted items. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Owner
|
Thanks @mattwhetton Closing this. |
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
2 participants
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.
Summary
beads-parser.tsandkanban-board.tsxto skip beads with unknown statuses instead of crashingProblem
The client crashed with
TypeError: Cannot read properties of undefined (reading 'push')when the backend returned beads with a status value (like "tombstone") that wasn't one of the 4 defined column statuses (open,in_progress,inreview,closed).Solution
Added defensive checks before pushing beads to grouped status arrays. Beads with unknown statuses are now silently skipped rather than causin a crash.