Repository navigation
Conversation
…ool results grid. pgadmin-org#8647 Bump the pinned react-data-grid fork to pick up shift + mousedown extending the selected range from the selected cell (pgadmin-org/react-data-grid#9), plus the change limiting shift + key range handling to shift + arrow keys when range selection is enabled (pgadmin-org/react-data-grid#10). Shift + click on the row number column is pgAdmin's row selection, so keep selecting that cell as a plain click does there. Otherwise a cell range selected earlier stays highlighted alongside the selected rows. Closes pgadmin-org#8647
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughThe query grid now intercepts Shift-mousedown on row-number cells to prevent the default range behavior and select the cell. The grid dependency is updated, and a regression spec covers this behavior and two non-intercepted cases. ChangesQuery grid selection
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Change: Feature · Severity of issue fixed: Low Merge Risk: ⚪ Minimal · up to
|
|
Squashed and merged as b98470f. |
Shift + click in the Query Tool results grid now extends the cell range from the selected cell, as shift + arrow keys already did.
This bumps the pinned react-data-grid fork to pick up pgadmin-org/react-data-grid#9 (shift + mousedown extends the range) and pgadmin-org/react-data-grid#10 (shift + key range handling only for shift + arrow with range selection on, range mouse handlers only attached when it is on, and a GroupRow/TreeDataGrid props fix). The
yarn.lockchange touches only react-data-grid.On the row number column, shift + click is pgAdmin's own row selection, so
onCellMouseDownnow selects that cell as a plain click does. Without that, a cell range selected earlier stayed highlighted alongside the selected rows.Test plan
QueryToolDataGridMouseDown.spec.js; the sqleditor and components Jest specs pass (--maxWorkers=2).Closes #8647
Summary by CodeRabbit