Fix kanban set previous neighbor - #13
Merged
Merged
Conversation
…and improve item selection logic
speerface
approved these changes
Feb 11, 2026
speerface
left a comment
Collaborator
There was a problem hiding this comment.
Tests are passing, and the switch to a deterministic result vs. the last-key fallback is a smart change, so I think this is good to merge. Let's just keep an eye on things to make sure something isn't borking elsewhere (but that should be pretty obvious in the UI). Thanks Paul!
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.
Description
This PR fixes setting previous neighbor for the kanban component.
Related Issue
Closes: #7104
Testing
Testing Requirements
Testing Instructions
QA Tracking Spreadsheet
Screenshots
Checklist
npm installand committed package-lock.json (if necessary).