-
Notifications
You must be signed in to change notification settings - Fork 84
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
LF-4084: Update table/2 to include checkboxes and row selection behaviour #3149
Merged
SayakaOno
merged 11 commits into
integration
from
LF-4084/Update_TableV2_to_include_checkboxes_and_row_selection_behaviour
Mar 7, 2024
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
852aa9d
LF-4084 add new color
SayakaOno 8e02be7
LF-4084 add checkbox to table, add story
SayakaOno 9cf1bdd
LF-4084 update V2 table to support sticky header
SayakaOno 6d9649d
LF-4084 remove table padding causing an issue with sticky header
SayakaOno cd66ab0
LF-4084 remove checkbox hover effect, cleanup stories
SayakaOno aae6e39
LF-4084 update TableV2Props type
SayakaOno bc0038c
LF-4084 add missing TableHead propTypes
SayakaOno 28c4759
Merge branch 'integration' into LF-4084/Update_TableV2_to_include_che…
SayakaOno ba375a5
LF-4084 update story
SayakaOno b7e0104
LF-4084 fix checkbox behaviour in table story
SayakaOno 1260716
Merge branch 'integration' into LF-4084/Update_TableV2_to_include_che…
SayakaOno 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 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 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 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 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
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.
I wonder if these two could be combined and simplified by passing a
setSelectedIds
function prop instead, and letting the table handle the different scenarios where the selected IDs need to changeThere 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.
It's possible, but I'm hesitant to do it.
A few of my concerns:
handleSelectAllClick
- we will have a function for this in its parent component anyways because we have "clear selection" in the action menuAre they not a big deal??
Update:
I figured that
handleSelectAllClick
should be like this:Considering we will have to write this in parent components, I am not sure which is better...
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.
Those are good points, this was just a suggestion but I think either way is alright!