Fix issue with monitor results pagination #5060
Merged
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.
Closes #PROD-2233
Description Of Changes
Fixes a bug where, when switching between pages using the result tables' pagination menu or searching, results from previous table views were remaining on the table.
Loom demonstrating bugged behavior
Loom demonstrating fixed behavior
The issue was that the
key
prop, which is used by React to determine which rows to clear when rerendering, wasn't unique enough-- if a result on page A had the same name as a result on page B, its row would stay on the table instead of being removed. I fixed this by making all discovery/detection tables also include their monitor config ID in their row ID (from which the key is derived).Code Changes
getRowId
across all D&D tablesgetRowId
to include monitor config IDdata-testid
sSteps to Confirm
Pre-Merge Checklist
CHANGELOG.md