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
DataTable 'Select All' does not overwrites previously selected #6973
base: master
Are you sure you want to change the base?
DataTable 'Select All' does not overwrites previously selected #6973
Conversation
Thanks for working on this @HardikChoudhary24! I think that when we have an option selected and then we search and the results doesn't include any of the selected options then we should just display an empty checkbox in the header rather than a checkbox with a @taysea @halocline feel free to jump in if you have any alternative opinions here |
This one probably warrants some discussion. When in a controlled mode, especially with onUpdate, the select list can contain keys that aren't in the current data and the header checkbox should reflect there are still some selections, but not all items are selected. This has ramifications for pagination situations. |
Good callout @MikeKingdom lets chat more about this Thursday during our grommet checkpoint meeting |
Hey @HardikChoudhary24 we really like the direction that this PR is heading! We chatted more as a team and want to evaluate some more complex examples of DataTable with pagination. No action items are needed on your end at this point, we just need some time to test and think through what is a reasonable default for different types of DataTables. Are you participating in Hacktoberfest? If so I would be happy to mark this pull request as 'hacktoberfest-accepted' |
Thanks @jcfilben for your feedback. I appreciate the offer to mark this PR as 'hacktoberfest-accepted', but I've already completed my Hacktoberfest contributions. Thank you for your understanding, Have a great day! |
What does this PR do?
Fixes #6946
Where should the reviewer start?
What testing has been done on this PR?
How should this be manually tested?
Do Jest tests follow these best practices?
screen
is used for querying.userEvent
is used in place offireEvent
.asFragment()
is used for snapshot testing.Any background context you want to provide?
What are the relevant issues?
#6946
Screenshots (if appropriate)
Screen.Recording.2023-10-15.at.11.36.45.PM.mov
Do the grommet docs need to be updated?
Should this PR be mentioned in the release notes?
Is this change backwards compatible or is it a breaking change?