Skip to content

7023-cb-find-and-replace-new#4085

Open
SychevAndrey wants to merge 64 commits intodevelfrom
7023-cb-find-and-replace-new
Open

7023-cb-find-and-replace-new#4085
SychevAndrey wants to merge 64 commits intodevelfrom
7023-cb-find-and-replace-new

Conversation

@SychevAndrey
Copy link
Contributor

@SychevAndrey SychevAndrey commented Jan 26, 2026

Screen.Recording.2026-01-28.at.15.37.39.mov

@SychevAndrey SychevAndrey self-assigned this Jan 27, 2026
@SychevAndrey SychevAndrey marked this pull request as ready for review January 28, 2026 11:45
SychevAndrey and others added 6 commits January 28, 2026 12:48
That functionality comes in handy when we want to use Undo and Replace All functions together:
Before that commit we used to perform N operations where N is a number of replaced cells. And history would record them as atomic operations, so pressing Undo would revert only the last replace.
setMany enables batch editing and batch reverting, so now we can Replace All and then revert it by using one Undo operation
Copy link
Contributor

@sergeyteleshev sergeyteleshev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All in all feature looks awesome! Nice integration with undo/redo btw

Please also consider cases with readonly tables (probably block replace functionality with disabled state) - Session Manager, readonly tables, tables where we cannot edit cells, but can add/delete rows

Also, keep in mind that if we replace 1 item. We want to scroll and focus this item because it may be outside the visible view, and we need to show the user that this value has changed. For "replace all" the view should remain the same (no selection, no scroll to cell)

Some of the issues can be resolved in the next tickets. We need to decide what we can do now and what later

Comment on lines +63 to +73
for (let rowIdx = 0; rowIdx < rowCount; rowIdx++) {
for (let colIdx = 0; colIdx < columnCount; colIdx++) {
const cellText = getCellText(rowIdx, colIdx);
if (searchPattern.test(cellText)) {
matches.push({ rowIdx, colIdx });
if (searchPattern.global) {
searchPattern.lastIndex = 0;
}
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well for big tables this would just crash the app due to performance issues in the worst case scenario. for most cases it would be like a freeze

we need something tricky here. maybe batch search in new thread (service worker)

I suppose not a bad idea to sync with the team how should we handle that so we do not dig into this real hard

also we have react-minisearch lib for searching. maybe it can offer something for us. we need to check the API for ideas

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image this simple solution still shows decent results even on huge tables. I would take it to separate ticket for further exploration.

I tried to use Web Worker for that calculations, but the bottleneck here is the getCellText which can't be called somewhere else. Batching, serializing/deserializing, orchestration adds too much overhead and didn't show any significant improvements. Actually, for me it even for worse

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We’ll need to come up with a solution anyway. Users with large datasets will definitely run into issues, but we can address performance problems on large datasets in a separate ticket. The main thing for now is that the new functionality should not affect users who don’t use the search and replace feature

Comment on lines +183 to +204
@@ -189,13 +199,20 @@ export const DataGridTable = observer<IDataPresentationProps>(function DataGridT
return;
}

if (dataGridRef.current?.isReplacing()) {
return;
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should revert that new behavior

As user I want to see all changes focused. For example we have huge table and our change is out of the screen right now. Currently if I replace 1 value I wont see what was replaced cause it was not scrolled or selected this cell. so we can miss something important

Comment on lines +39 to +40
this.compressLastEditedCellHistory(data.key);
const singleUpdateKey = data.updates.length === 1 ? data.updates[0]!.key : undefined;
this.compressLastEditedCellHistory(singleUpdateKey);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we use if here and restrict passing undefined to the compressLastEditedCellHistory because it make no sense

Comment on lines -174 to 217
if (rowsCountRef.current !== rowsCount) {
const previousRowCount = rowsCountRef.current;
rowsCountRef.current = rowsCount;
if (prevRowsCount !== rowsCount) {
setPrevRowsCount(rowsCount);

if (previousRowCount === 0) {
if (prevRowsCount === 0) {
setColumnWidths(new Map<string, ColumnWidth>());
}
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SychevAndrey and others added 14 commits February 24, 2026 10:49
…andle

Replaced onCellClassNameChange prop + useEffect with useImperativeHandle as suggested in code review. Using useState setter directly as callback ref either caused infinite re-renders (without deps) or lost context synchronization entirely (with stable deps). Settled on useCallback ref that sets both useRef (for method access) and useState (for context propagation).
…id component

Previously DataGridTable checked isReplacing() before syncing
focus/selection, leaking grid internals
Now the grid's selectCell blocks during replacing internally and
supports deferred mode (setTimeout + rAF) for post-render focus sync.
moved ref synchronization out of render,
unified search+scroll into one shared path,
added a SET_MATCHES no-op guard to reduce unnecessary updates,
removed duplicate open=false persistence from useDataGridSearch (single owner now in useGridSearch).
@SychevAndrey SychevAndrey requested a review from Wroud February 25, 2026 16:04
@SychevAndrey SychevAndrey requested a review from Wroud February 27, 2026 09:05
handlers.focusCell(data.key);
setTimeout(() => restoreFocus(), 1);
}, 1);
handlers.focusCell(data.key, false, true);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we fixed the old behaviour in different way?

  1. Choose cell
  2. Press duplicate row
  3. Focus should be on the row
  4. We can navigate through editor using keyboard

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Screen.Recording.2026-03-03.at.10.59.19.mov

Yes, it was exactly like you described

Wroud
Wroud previously approved these changes Mar 3, 2026
Comment on lines 454 to 460
useEffect(
() => () => {
cellListenersRef.current.clear();
clearTrackedCellSubscriptions();
},
[],
[clearTrackedCellSubscriptions],
);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you have this logic in the useTrackedGridSearchCellSubscriptions already so you don't need it here

…ions

Cleanup implemented in useTrackedGridSearchCellSubscriptions hook
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants