Skip to content
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

Header grouping - Table component #10844

Open
1 task done
eranga93 opened this issue Feb 12, 2025 · 4 comments
Open
1 task done

Header grouping - Table component #10844

eranga93 opened this issue Feb 12, 2025 · 4 comments
Labels

Comments

@eranga93
Copy link

eranga93 commented Feb 12, 2025

Is your feature request related to a problem?

Currently the Table component doesn't support Header grouping. The table component we are trying to implement has multiple headers and grouping.

Image

Describe the solution you'd like

As shown on the image above, the Header should support multi layers and grouping.

Describe alternatives you've considered

None of the table components available on UI5 currently supports group headers, It's possible with the HTML5 table component https://developer.mozilla.org/en-US/docs/Web/HTML/Element/th

Additional Context

No response

Organization

SAP Signavio

Declaration

  • I’m not disclosing any internal or sensitive information.
@Lukas742
Copy link
Collaborator

Thanks for reporting! I'll forward this issue to our UI5 Web Components Colleagues as the affected component is developed in their repository.

@Lukas742 Lukas742 transferred this issue from SAP/ui5-webcomponents-react Feb 13, 2025
@dobrinyonkov
Copy link
Contributor

Hello @SAP/ui5-webcomponents-table,

could you please check this feature request?

Kind Regards,
Dobrin

@simlin
Copy link

simlin commented Feb 13, 2025

Hi,

we have the functionality of merged headers in the GridTable in UI5 classic as well. So the feature request is valid.
But in UI5 there maybe just about 0,05% of the usecases use this functionality. So the priority is low and I don't expect this to come soon.

Best Regards
Jens

@steffektif
Copy link

steffektif commented Feb 17, 2025

Hey there,

I'm with @eranga93. We're working on a topic that is customer relevant where we have a commitment made for end of Q2. I see that the prio might be low because of low usage. We unfortunately don't have any chance to use anything but the react wrapper and of course we want to also hold our commitment.

Any chance to set this to a higher prio, or are your prios exclusively decided by usage? In case you can't can we contribute to make it happen?

Edit: In case you need more info, we can also provide more info for our use case etc.

Best

Stef

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

No branches or pull requests

5 participants