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

Consider using a table format #36

Open
recht opened this issue Aug 24, 2023 · 3 comments
Open

Consider using a table format #36

recht opened this issue Aug 24, 2023 · 3 comments
Labels
good first issue Good for newcomers

Comments

@recht
Copy link

recht commented Aug 24, 2023

The list views (claims, compositions, managed resources, etc) are not very space-efficient, so once you have more than just a couple of items, you need to scroll, and it's hard to get an overview. Consider instead using a more dense table format, maybe even one that supports sorting/filtering

@undera
Copy link
Collaborator

undera commented Aug 25, 2023

I agree, this is already mentioned in Roadmap document.

@undera undera added the good first issue Good for newcomers label Aug 25, 2023
@rezuma
Copy link

rezuma commented Mar 14, 2024

This would be very useful for troubleshooting. How far away is this in the roadmap? I would be willing to work on it

@undera
Copy link
Collaborator

undera commented Mar 15, 2024

@rezuma It's as close as you make it ;)
If you are willing to work on it - feel free to bring PRs for review. It would be very nice to have it implemented.

undera pushed a commit that referenced this issue Aug 26, 2024
…resources (#67)

* Accordion style presentation of composite resources.

* Resolve linter issue: call useState hook conditionally
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants