Repository navigation
Conversation
13 tasks
|
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 8 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
3 tasks done
arikfr
force-pushed
the
fe/10-dnd-kit
branch
from
September 28, 2026 09:42
6b64b59 to
30cd808
Compare
arikfr
force-pushed
the
fe/09-react-testing-library
branch
2 times, most recently
from
September 28, 2026 14:57
04c02f3 to
d69ade9
Compare
arikfr
force-pushed
the
fe/10-dnd-kit
branch
2 times, most recently
from
October 3, 2026 21:06
e283e33 to
c172e43
Compare
arikfr
force-pushed
the
fe/09-react-testing-library
branch
from
October 3, 2026 21:06
d69ade9 to
2b063e4
Compare
arikfr
force-pushed
the
fe/09-react-testing-library
branch
from
October 4, 2026 13:56
2b063e4 to
9997fa9
Compare
react-sortable-hoc is unmaintained, only allows React 16/17, and relies on findDOMNode, which React 19 removes. Reimplement viz-lib's sortable components (SortableContainer, SortableElement, sortableElement, DragHandle) on @dnd-kit, keeping their API: items are identified by index and the container reports `onSortEnd({ oldIndex, newIndex })`. - Items move in place instead of being cloned into a floating "helper"; `helperClass` is applied to the dragged item. - The drag handle finds its item's DOM node with closest(), which works for components that don't expose a DOM ref (antd's Collapse.Panel). - Mouse and touch sensors (the e2e tests drag with mouse events), plus keyboard sorting. - The container takes an `itemCount`. Parameters' `appendSortableToParent` (where to attach the helper) and the undefined `onBeforeSortStart` handler are gone. Part of #7848. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
arikfr
force-pushed
the
fe/09-react-testing-library
branch
from
October 8, 2026 12:36
9997fa9 to
4a85a9d
Compare
This branch has not been deployed
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.
What type of PR is this?
Description
Part 10 of the frontend dependency upgrade stack tracked in #7848. Stacked on #7859.
react-sortable-hochasn't had a release since 2022. It only allows React 16/17 and usesfindDOMNode, which React 19 removes. This reimplements viz-lib'scomponents/sortableon dnd-kit (@dnd-kit/core,sortable,modifiers,utilities; all support React 16.8–19).The API stays the same (
SortableContainer,SortableElement,DragHandle, plus a localsortableElement()HOC instead of react-sortable-hoc's). Items are identified by index, and the container reportsonSortEnd({ oldIndex, newIndex }). It's used in three places: query/dashboard parameters, the chart editor's series order, and the table/details editors' column order.What's different
helperClassgoes on the dragged item. Parameters'appendSortableToParentprop only chose where that clone was attached, so it's gone. So is theonBeforeSortStarthandler, which didn't exist on the component.DragHandlefinds it withclosest(), which works for components that don't expose a DOM ref, like antd'sCollapse.Panel(react-sortable-hoc usedfindDOMNode).role="button"and screen reader instructions.itemCountprop, since dnd-kit needs the list of item ids up front.How is this tested?
Unit tests (pytest, jest)
Manually
Lint, type-check, jest and the production build pass locally.
New unit tests for the sortable components: mouse drag (with a mocked layout, since jsdom doesn't lay anything out), the
sortableElementHOC, the dragging classes, keyboard sorting and the disabled state.In Chromium (Playwright, real mouse), against a local backend, I reordered:
No console errors.
The Cypress "rearrange parameters" test runs on the canary ([Do not merge] CI for the frontend dependency upgrade stack (#7848) #7852).
🤖 Generated with Claude Code