Add custom header icons (in the style of sortable, filterable, toggleable)

[noxan]

Describe the solution you'd like
I'd love to add custom header actions (icons) in the style of sortable, filterable, toggleable. Filter comes closest, as it allows to show a custom overlay, I'd like to take it a step further and allow any kind of action handler, custom icons, possibly a render function, etc.

Use cases are for example:

• Edit: rename the column title
• Remove: similar to toggle, but custom logic
• Move left/right: without drag and drop, shift the column to the left or right

Or potentially even allow to override the default implementations (for sortable, filterable, toggleable) in order to put them into a context menu (nesting) or override their default behavior.

Describe alternatives you've considered
Hijacked the filter feature to add custom buttons within its render function. It works, but not really the right icon (no way to override that), nor the intended use case.

Alternatively was considering to use the onContextMenu for header columns. The event triggers, but there weren't any examples on how to use it for the header column and I don't need it anywhere else yet, so wanted to avoid the extra dependency and overall overhead.

Additional context
Depending on how we implement this, it could add a lot of overhead and unnecessary complexity. Maybe there is a more clever way to achieve this? Also might make sense to have some collapse feature (if there are too many header action icons, they get moved into a context menu) or only allow custom header actions within a context menu (one icon with three dots visible, opens a popover) by default.

[noxan]

PS: Happy to help with the implementation, but would love feedback on the approach first. Here a short sketch in code of what it might look like main...noxan:mantine-datatable:main

[icflorescu]

I'm a bit up to my ears in a commercial project at the moment (oss maintainers have to eat too 😉), but I like the idea, so I'm open to a PR on the matter. I am a bit worried about the added overhead, though.

[noxan]

@icflorescu thanks for being so transparent and highly appreciate how responsive you are given the situation :)

I will draft a first attempt and try to keep it simple. If you have any considerations or constraints (as I'm quite new to this project) I'd be glad to hear and learn. I'll give you an update about next week with some code and thoughts.