Column Resizing For Groups and Nested Tables
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
No source files, tests, or entry points are named. Start by reproducing the grouped-column and nested-table resizing cases described in the issue, then trace the existing resize behavior for parent and child columns. Done should provide a clear way to resize grouped columns and keep parent and child widths matched without broken layout.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
We are using collapsible nested tables for our customer facing UI. We are also making use of the groups feature to group columns together. We are using fixed widths to match parent and child column widths. But this means that some data gets truncated. We would like to use the resize functionality - but when we resize the parent column, the child column mismatches and leads to broken UI. Also the resize icon does not appear in the title cell in the group, and with only one column - this is not where a user would expect it to be.
Describe the solution you'd like
I would like the resize icon to appear in the top title cell in groups (with one column) or an option of this sort.
I would like to be able to match parent and child column widths.
Describe alternatives you've considered
I tried setting the keys of both tables to the the same key, but since column accessors are different, that did not work.
Additional context
Resize bar appearing in column name instead of top group
Resizable columns mismatch
Is this feature expected anytime soon?
Would also be interested in contributing to a PR if something like this is coming up.
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 102
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from icflorescu/mantine-datatable
-
table shadow ios bug Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
icflorescu/mantine-datatable#791 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
icflorescu/mantine-datatable#844 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
icflorescu/mantine-datatable#835 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
icflorescu/mantine-datatable#833 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
icflorescu/mantine-datatable#826 ·
All issues in icflorescu/mantine-datatable
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·