-
Notifications
You must be signed in to change notification settings - Fork 15
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
Cluster details updates #2328
Cluster details updates #2328
Conversation
8c7ea63
to
cb559f8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @rtorrero
Only one thing. With the rounded table thing, the header row shouldn't be rounded when there is an additional header on top of it.
Besides that, all of the table in the app are rounder now, and I don't think this was desired. We should have some rounder option as prop in the Table component I guess to make it variable.
What do you think @jagabomb ?
PD: by the way, if we agree that all tables should be rounder, we wouldn't need to "rounder" variable. Fixing the header would be enough
Well spotted @arbulu89, yeah only the top and bottom sections of the Site Detail component should be rounded. So in this case the, Site Name (NBG/WDF) would be the top part of the component with the top rounded corners. Then the grey Table Header (Hostname, Nameserver, etc) without any rounded corners. Followed by the Table Description with bottom rounded corners. This styling helps to make the Sites Detail nodes feel like single components. |
once #2337 is merged, I'll adjust this and re-request review 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, you survived the CSS war.
LGTM!
cb559f8
to
e9af002
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rtorrero
Looks good.
Please add a test to the StoppedResources
view, for the 0 resources scenario.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM... Nice one!
1ebe81b
to
ec2ec3b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please change the import.
We are fine to merge afterwards
* Change Node Details header * Add top margin for subheaders and remove no longer needed button import * Move stopped resources and always display even when empty * Adjust test to match new name for header * Style button as a link * Use new header prop in table component * Add stopped resources test scenario for no stopped resources
Description
This PR adds some of the UI changes proposed by @jagabomb:
See attached screenshots for more details: