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

Separate data inside failed message time stamp #325

Closed
sergioc opened this issue Apr 4, 2016 · 5 comments
Closed

Separate data inside failed message time stamp #325

sergioc opened this issue Apr 4, 2016 · 5 comments
Labels
Type: Feature Type: Feature
Milestone

Comments

@sergioc
Copy link
Contributor

sergioc commented Apr 4, 2016

2016-04-04 at 18 17

In the metadata element above you can read 3 different types of metadata in one long sentence, which makes it hard to read. This can be presented better by chunking the metadata like this:

  • Failed:
  • Endpoint:
  • Machine:
@sergioc sergioc added the Type: Feature Type: Feature label Apr 4, 2016
@WojcikMike
Copy link
Contributor

@sergioc your proposition would be easier to ready but also would take more space.

What if we would go with:
Failed: 5 minutes ago | Endpoint: SmoteTest.Server | Machine: RAMON-HOME

In that case:

  • we keep the same information
  • the same amount of place taken
  • easier to make responsive (replace labels with icons for example)

What do you think?

@sergioc
Copy link
Contributor Author

sergioc commented Jun 1, 2016

@WojcikMike my proposal is just to chunk. I didn't propose a specific layout.

In any case, I agree the ideal is to keep as much as possible in one line.

@sergioc
Copy link
Contributor Author

sergioc commented Jun 1, 2016

I do not agree with replacing labels with icons on mobile, though, especially not on mobile where you lose the ability to hover on icons to get tooltips.

@WojcikMike WojcikMike added this to the 1.6.7 milestone Sep 9, 2016
@WojcikMike
Copy link
Contributor

This issue is solved as a part of #364

@WojcikMike
Copy link
Contributor

@sergioc please reopen if you think that we should do more in that matter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Type: Feature
Projects
None yet
Development

No branches or pull requests

2 participants