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

Allow customizing columns #757

Closed
fujiapple852 opened this issue Nov 3, 2023 · 2 comments · Fixed by #863
Closed

Allow customizing columns #757

fujiapple852 opened this issue Nov 3, 2023 · 2 comments · Fixed by #863
Labels
enhancement New feature or request tui
Milestone

Comments

@fujiapple852
Copy link
Owner

fujiapple852 commented Nov 3, 2023

The list of columns shown in the main table is fixed. It would be nice if users could customise this list.

This would likely take the form of:

  • A command line / config file entry to specify a list of columns to show in the Tui and reports
  • A dialog in the Tui to allow modification of the columns shown in the Tui

It may also be useful to allow adjusting the format of the data in each column and perhaps even the column widths.

@trkelly23
Copy link
Collaborator

As you mentioned in the issue #39 it would be better to work 757 first.
I totally agree this feature is needed before adding more columns to the frontend.

@trkelly23
Copy link
Collaborator

I published the first changes for the custom columns. So far it allows for command line and config file choices of columns by selecting single characters. It doesn't customization of individual headings there are challenges in borrowing custom column headings &str values due to the &mut app passed into the table.rs render call.
If you don't mind can I get some quick feedback on:
https://github.com/trkelly23/trippy/tree/Allow-Custom-Columns
** Not quite ready for a PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tui
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants