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

Multiple row selection in table component #11404

Closed
RaphaelChauveau opened this Issue Jul 22, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@RaphaelChauveau
Contributor

RaphaelChauveau commented Jul 22, 2018

  • I have searched the issues of this repository and believe that this is not a duplicate.

What problem does this feature solve?

When working with the table component, I sometimes have to select a large number of contiguous rows. To do that, we currently have to select each row independently. This process can be very long and painstaking.

In order to facilitate the selection or unselection of multiple contiguous rows, I propose a new feature to allow multiple row selection/unselection.

To (un)select multiple rows, click the checkbox of the first row and shift-click the checkbox of the last row. All the rows located between the first and the last rows shall be (un)selected. If the last row was selected, the rows shall be unselected and if it was unselected, the rows shall be selected. The described behavior is the same as the Google Gmail application.

What does the proposed API look like?

The rowSelection config should handle a new type of callback : onSelectMulti.

This callback should be called when rows are (un)selected using the multiple row (un)selection feature. The callback should have the same type as the onSelectAll callback (Function(selected, selectedRows, changeRows))

yesmeck added a commit that referenced this issue Jul 24, 2018

Multiple row selection (#11406)
This PR intends to solve issue #11404 (Multiple row selection in table component).

The Chinese documentation is missing from the PR. Could someone please add it ?

@afc163 afc163 closed this Jul 29, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment