Row action buttons in Advanced example do not work correctly when all rows are selected

[sijonelis]

mantine-react-table version

2.0.0-beta.4

react & react-dom versions

18.2.0

Describe the bug and the steps to reproduce it

Go to the advanced example page: https://v2.mantine-react-table.com/docs/examples/advanced#advanced-example and

1. No rows selected: action buttons are inactive
2. Select one row. The action buttons become active
3. Filter out a single row by the exact filter match (see screenshot 1): buttons become inactive (they shouldn't!)
4. Make the filter more ambiguous to contain >1 row: buttons become active (see screenshot 2)
5. Click "select all": action buttons become inactive again (see screenshot 3). (they shouldn't!)

Minimal, Reproducible Example - (Optional, but Recommended)

Provided in repro: https://v2.mantine-react-table.com/docs/examples/advanced#advanced-example

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

Maybe, I'll investigate and start debugging

Terms

• I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

[sijonelis]

Upon digging deeper into Tanstack docs, it is an issue within their API.

While their documentation states that

getIsSomeRowsSelected: () => boolean
Returns whether or not any rows in the table are selected.

It is mutually exclusive with getIsAllRowsSelected

Thus currently the "correct "way to render the advanced example should be:

... same for other buttons 
<Button
              color="blue"
              disabled={!table.getIsSomeRowsSelected()  && !table.getIsAllRowsSelected()}
              onClick={handleContact}
              variant="filled"
            >
              Contact
</Button>

Tanstack tables repo already has an issue to track this, so hopefully this will be fixed in the future release.
Keeping that in mind I think it is not worth it to do any changes on this project's examples, just have to keep this in mind until the issue is fixed on the Tanstack side.

I'll leave it up to the team whether to keep this issue open or close it~