Skip to content

Various small UI naming tweaks#234

Merged
rmars merged 3 commits intomasterfrom
rmars/ui-small-fixes
Feb 1, 2018
Merged

Various small UI naming tweaks#234
rmars merged 3 commits intomasterfrom
rmars/ui-small-fixes

Conversation

@rmars
Copy link

@rmars rmars commented Jan 30, 2018

  • align top two tables in the service mesh page
  • "All Deployments" -> "Deployments"
  • reorder latency p50, p95, p99
  • "Current success" -> "Success rate"

Signed-off-by: Risha Mars [email protected]

- align top two tables in the service mesh page
- "All Deployments" -> "Deployments"
- reorder latency p50, p95, p99
- "Current success" -> "Success rate"

Signed-off-by: Risha Mars <[email protected]>
@rmars rmars added the area/web label Jan 30, 2018
@rmars rmars self-assigned this Jan 30, 2018
@rmars rmars added the review/ready Issue has a reviewable PR label Jan 30, 2018
.service-mesh-table {
margin-top: 18px;
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a big improvement. I wonder if we want to do the same for .incomplete-mesh-message, .complete-mesh-message. We could add a 32px top margin to those classes to line them up with the header of the Data Plane table. This is how it looks now:

image

And with 32px padding:

image

What do you think?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah, that looks better to me! will do!

<div className="current-latency">
{
_.map(["P99", "P95", "P50"], latency => {
_.map(["P50", "P95", "P99"], latency => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As part of this change can we also reorder the latency columns in TabbedMetricsTable:

image

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh yeah! forgot about those, thanks!

Copy link
Member

@siggy siggy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm modulo kevin's feedback.

something for this branch or a subsequent ui fixup, the Components number looks a bit out of place. perhaps the value should be right-justified, or, something else?

screen shot 2018-01-30 at 11 39 47 am

@rmars
Copy link
Author

rmars commented Jan 30, 2018

whoa good catch, those are supposed to be right aligned.

Signed-off-by: Risha Mars <[email protected]>
@rmars rmars force-pushed the rmars/ui-small-fixes branch from 04389c8 to bceeb8a Compare January 30, 2018 20:34
Copy link
Contributor

@klingerf klingerf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⭐️ Great! Thanks for making those updates.

@rmars rmars merged commit f3925a0 into master Feb 1, 2018
@rmars rmars removed the review/ready Issue has a reviewable PR label Feb 1, 2018
@rmars rmars deleted the rmars/ui-small-fixes branch February 1, 2018 02:09
hawkw pushed a commit that referenced this pull request Feb 1, 2018
* README update to 2018 (#233)

Signed-off-by: Andrew Seigner <[email protected]>

* Prepare for v0.2.0 release (#248)

* prepare for v0.2.0 release

Signed-off-by: Dennis Adjei-Baah <[email protected]>

* Use dots reporter instead of nyan reporter in CI (#238)

Signed-off-by: Risha Mars <[email protected]>

* Various small UI tweaks (#234)

* Various small UI naming tweaks

- align top two tables in the service mesh page
- "All Deployments" -> "Deployments"
- reorder latency p50, p95, p99
- "Current success" -> "Success rate"

* Add margin to incomplete mesh message, reorder latency in TabbedMetricsTable
* Right align numbers in service mesh page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants