-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[OPIK-8021] [QA] Proposed e2e specs for the virtualized traces table (from #7947 exploration) #7970
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
CometActions
wants to merge
6
commits into
main
from
comet-qa-bot/OPIK-8021/traces-table-virtualization-e2e
Closed
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
6d77e64
[OPIK-8021] [FE] perf: virtualize the traces table's columns and rows
andriidudar e37a75f
fix(data-table): decide column and row virtualization independently
andriidudar d5b3f19
test(data-table): cover sliceColumnWindow spacer edges
andriidudar 6232ebb
fix(traces-table): unify column and row virtualization into one condi…
andriidudar 4b66cdd
fix(data-table): memoize skeleton column window, cover slicer edge cases
andriidudar fc820f4
[OPIK-8021] [QA] e2e: cover the virtualized traces table's row and co…
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
23 changes: 23 additions & 0 deletions
23
apps/opik-frontend/src/shared/DataTable/columnVirtualization/ColumnSpacerCell.tsx
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| import React from "react"; | ||
|
|
||
| import { ColumnSpacer } from "@/shared/DataTable/columnVirtualization/columnWindow"; | ||
|
|
||
| type ColumnSpacerCellProps = { | ||
| spacer: ColumnSpacer; | ||
| isHeader?: boolean; | ||
| }; | ||
|
|
||
| const ColumnSpacerCell: React.FC<ColumnSpacerCellProps> = ({ | ||
| spacer, | ||
| isHeader, | ||
| }) => { | ||
| const style = { padding: 0, border: 0, width: `${spacer.size}px` }; | ||
|
|
||
| return isHeader ? ( | ||
| <th aria-hidden style={style} /> | ||
| ) : ( | ||
| <td aria-hidden style={style} /> | ||
| ); | ||
| }; | ||
|
|
||
| export default ColumnSpacerCell; |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default tables ignore row virtualization
When
TableBodyis the defaultDataTableBody, it acceptsrowVirtualizationbut always renderstable.getRowModel().rows.map(renderRow), soDataTablecallers usingrowVirtualization={{ enabled: true }}withoutDataTableVirtualBodyrender every row — should we selectDataTableVirtualBodyautomatically?Want Baz to fix this for you? Activate Fixer
Other fix methods
Prompt for AI Agents