Skip to content
This repository was archived by the owner on Nov 6, 2020. It is now read-only.

Wrong version on status page #1860

Closed
nerdralph opened this issue Aug 7, 2016 · 5 comments · Fixed by #1915
Closed

Wrong version on status page #1860

nerdralph opened this issue Aug 7, 2016 · 5 comments · Fixed by #1915
Assignees
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow.
Milestone

Comments

@nerdralph
Copy link

http://127.0.0.1:8080/home/ says:
"Status Page for Parity 0.6.0"
I'm running v1.2.3-beta

@rphmeier
Copy link
Contributor

rphmeier commented Aug 7, 2016

This is the version of the status page itself: https://github.com/ethcore/parity-ui/blob/master/status/Cargo.toml#L4

@nerdralph
Copy link
Author

It's bad user interface design if you are exposing internal component versions.

@gavofyork
Copy link
Contributor

agreed.

@gavofyork gavofyork added the F2-bug 🐞 The client fails to follow expected behavior. label Aug 7, 2016
@gavofyork gavofyork added F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. and removed F2-bug 🐞 The client fails to follow expected behavior. labels Aug 7, 2016
@gavofyork gavofyork added this to the 1.4 Civility milestone Aug 7, 2016
@rphmeier
Copy link
Contributor

rphmeier commented Aug 7, 2016

The page shows the version in a much less visible font color than the issue here would imply; I agree it's a UI design issue but not a particularly severe one. Probably just a simple rephrase will provide the desired clarity.

@gavofyork
Copy link
Contributor

internal versions shouldn't be exposed in the user interface.

@gavofyork gavofyork added the Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow. label Aug 9, 2016
@tomusdrw tomusdrw self-assigned this Aug 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F3-annoyance 💩 The client behaves within expectations, however this “expected behaviour” itself is at issue. Q2-easy 💃 Can be fixed by copy and pasting from StackOverflow.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants