Manine v9 Support

[QuaduxIT]

mantine-react-table version

2.0.0-beta.9

react & react-dom versions

19.2.x

Describe the bug and the steps to reproduce it

Summary

When using mantine-react-table@2.0.0-beta.9 with Mantine v9 (@mantine/core@9.0.0-alpha.0), React logs:

Received true for a non-boolean attribute in.

The warning appears to come from internal Collapse usage still using the Mantine v8 prop in.

Environment

• mantine-react-table: 2.0.0-beta.9
• @mantine/core: 9.0.0-alpha.0
• React: 19.2.x
• Next.js: 16.1.x

Reproduction

1. Install mantine-react-table@2.0.0-beta.9
2. Install Mantine v9 alpha (@mantine/core@9.0.0-alpha.0)
3. Render a table with one or more of these features:
   • detail panel
   • global filter
   • column filters
   • toolbar alert banner
   • progress bar
4. Open browser console

Actual behavior

Console warning appears:

Received true for a non-boolean attribute in.

Expected behavior

No React warning. Mantine v9-compatible props should be used.

Root cause

Mantine v9 renamed Collapse prop from in to expanded.
Current MRT internals still pass in.

Proposed fix

Replace all internal usages:

// before
<Collapse in={condition}>...</Collapse>

// after
<Collapse expanded={condition}>...</Collapse>

### Minimal, Reproducible Example - (Optional, but Recommended)

### PR Title
fix(mantine-v9): replace `Collapse in` with `Collapse expanded`

### PR Description
```md
## What

This PR updates internal `Collapse` usages for Mantine v9 compatibility:
- `in` -> `expanded`

## Why

Mantine v9 renamed the `Collapse` control prop from `in` to `expanded`.
With current code, React logs warning:

`Received true for a non-boolean attribute in.`

## Scope

Updated all known internal `Collapse` usages in MRT runtime paths:
- detail panel
- table head filter container
- toolbar alert banner
- global filter
- progress bar

## Validation

- Reproduced warning before patch using Mantine v9 alpha
- Applied rename (`in` -> `expanded`)
- Verified warning no longer appears

## Breaking changes

None intended. This is a compatibility fix for Mantine v9 behavior.

## Checklist

- [x] Reproduced issue
- [x] Applied focused fix
- [x] Verified warning removed
- [x] No API surface changes introduced

### Screenshots or Videos (Optional)

Thanks for maintaining this package.
I can confirm this warning is resolved locally by replacing internal `Collapse in` with `Collapse expanded` for Mantine v9.
If helpful, I can open a PR with the change.

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

Yes, I think I know how to fix it and will discuss it in the comments of this issue

### Terms

- [x] 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.

[chris-edstrom]

I've created a Mantine 9/React 19 fork here: https://github.com/CareHarmony/mantine-react-table. You can point your npm at the repo at https://github.com/CareHarmony/mantine-react-table-ch until such time as I decide to publish it on npm.

[eastack]

Is this going to be a separate project in the future, or will it get merged back into the current one?

[chris-edstrom]

I'm willing to contribute back the changes, but issue #538 still remains which forced me to fork in the first place.

[BrendanC23]

Mantine version 9.0.0 has been released.