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

Augment the table control's columns capabilities #1439

Open
1 of 5 tasks
FabienLelaquais opened this issue Jun 21, 2024 · 3 comments
Open
1 of 5 tasks

Augment the table control's columns capabilities #1439

FabienLelaquais opened this issue Jun 21, 2024 · 3 comments
Labels
🖰 GUI Related to GUI 📈 Improvement Improvement of a feature. 🟩 Priority: Low Low priority and doesn't need to be rushed 📝Release Notes Impacts the Release Notes

Comments

@FabienLelaquais
Copy link
Member

FabienLelaquais commented Jun 21, 2024

Description

The columns property of table can be set to a dictionary where, for every column, one can customize:

  • The number or date format to apply
  • The title of the column
  • The index where it should appear in the table.

This issue is about considering adding support for all indexed properties of the table:

  • group_by, set to the name of the aggregation function, would indicate the table would perform an aggregation on this column using this function;
  • style, if set to a string, would add it as a CSS class to this column's cells;
  • tooltip, if set to some text, would be the text used when the column is hover over;
  • filter, if set to True, allows for filtering on this column;
  • nan_value, if set to some text, would have the table use that as the representation for a 'no value' cell;
  • editable, if set to True, allows for editing this column;
  • lov could be set to a list of string values that are allowed for this column.
  • width could be set to force the width of this column.

Setting columns[<column_name>].<property> would overwrite a potential table.<property>[<column_name>].

Note that we may also want to add the indexed title property to table... for homogeneity.

Acceptance Criteria

  • Ensure new code is unit tested, and check code coverage is at least 90%.
  • Propagate any change on the demos and run all of them to ensure there is no breaking change.
  • Ensure any change is well documented.

Code of Conduct

  • I have checked the existing issues.
  • I am willing to work on this issue (optional)
@FabienLelaquais FabienLelaquais added 📈 Improvement Improvement of a feature. 🖰 GUI Related to GUI 🟩 Priority: Low Low priority and doesn't need to be rushed labels Jun 21, 2024
@FredLL-Avaiga
Copy link
Member

ColumnDesc interface definition is here

@FabienLelaquais FabienLelaquais added the 📝Release Notes Impacts the Release Notes label Jun 22, 2024
@pravintargaryen
Copy link

can i take this?

@jrobinAV
Copy link
Member

@pravintargaryen Our core maintainer team has not reviewed this issue. We will let you know as soon as possible if we want to implement it.
Thank you for your understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖰 GUI Related to GUI 📈 Improvement Improvement of a feature. 🟩 Priority: Low Low priority and doesn't need to be rushed 📝Release Notes Impacts the Release Notes
Projects
None yet
Development

No branches or pull requests

4 participants