-
Notifications
You must be signed in to change notification settings - Fork 708
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
Refactor table views #848
Comments
I also think we may want to revisit whether we want tables in certain cases, there may be better ways to display some of the information we're showing. A table, to me, gives the impression of detailed information, when the goal of Kubeapps is to make things simple and consumable. |
Yes, but probably to display better information we may need more metadata from the chart (like knowing which secrets are credentials). In any case, I think that having raw information about all the resources for an app is something useful. Advanced users/developers can use that to see what's going on. |
Potentially, but I would see that level of detail as a cluster operator concern, not an app dev concern. I think it's useful to have it in a different tab for advanced info, but it should not be in the default view. Anyway, I think I'm getting away from the point of this issue, which is to create a common component we can reuse for similar views, which I do think is valuable for when we do want to show tabular information. We may want to look at if there are any React components out there that make showing tabular data easier. |
yes @lindhe, that seems like a bug. Do you mind opening a different PR? we can fix the style there. |
New UI has app resources in a standard table with tabs. |
We have several views in which we render tables like the Services, Deployments, Secrets, etc. of the AppView or the bindings in the ServiceView. Each of them has mostly the same component that represents the table but changing the columns content. We can create a generic component out of it.
I think we should also review the representation, I think that having a single box with different tabs for showing the different tables will provide a better UX in some cases (like the app resources).
The text was updated successfully, but these errors were encountered: