-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[UI v2] feat: Re-organizes flow runs data table components and to use a provider for row selection capabilities #17216
Conversation
5183359
to
370918e
Compare
… a provider for row selection capabilities
370918e
to
ea62c35
Compare
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.
Fixes bug from mismatched values
|
||
const selectedRows = Object.keys(rowSelection); | ||
if (rowSelectionCtx) { |
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.
Here's the logic to give the data-table the selectable UX. Dependent if its wrapped with a row-selection provider
<ViewComponent key={value} /> | ||
))} | ||
</Tabs> | ||
); | ||
}; | ||
|
||
function useBuildTabOptions(deployment: Deployment) { | ||
return useMemo( |
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.
Needed to memo-ize this to prevent the entire tab component to re-render and losing input focus
Thanks for cleaning this up! |
… a provider for row selection capabilities (#17216)
Re-organizes flow runs data table components and to use a provider for row selection capabilities
Uploading Screen Recording 2025-02-20 at 10.21.10 AM.mov…
Checklist
<link to issue>
"mint.json
.