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

Introduce a flexible way to configure data table column widths #1296

Open
1 of 3 tasks
ndickerson opened this issue Apr 21, 2022 · 0 comments
Open
1 of 3 tasks

Introduce a flexible way to configure data table column widths #1296

ndickerson opened this issue Apr 21, 2022 · 0 comments
Labels
enhancement improvements to existing functionality that have never existed before

Comments

@ndickerson
Copy link
Member

Describe the solution you'd like
Right now the options for configuring data table column widths are:

  1. Use the default - all columns have equal width that is shared as the total width expands
  2. Set a fixed pixel width for some columns, leaving the rest to equally expand
  3. Custom CSS solution at the consumer level

In order to accommodate readability at various screen resolutions, when a data table needs widths that grow at different rates (flex 1, flex 1.5, etc) then option 3 would be the only alternative.

A fourth option would be very helpful - instead of just allowing the column.width parameter in the column definition, allow a column.flexWidth (a.k.a: flex, flexibleWidth, flexBasis). The value provided could be passed through to the table as the percentage of total width that the column consumes. This could be a percentage for each column, or any of the other options that flex provides.

Will this feature require a breaking change?
Does your feature request require breaking changes to existing functionality of current components or services?

  • Yes
  • No
  • Not sure

Alternative solutions
Option 3 above

Will this feature require a change to dependencies?
No

Additional context
This feature is being implemented in Novo, and will probably be re-implemented many times unless we can solve the root cause here in Novo Elements.

@michael-amaya-bh michael-amaya-bh added enhancement improvements to existing functionality that have never existed before and removed feature labels Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement improvements to existing functionality that have never existed before
Projects
None yet
Development

No branches or pull requests

3 participants