-
Notifications
You must be signed in to change notification settings - Fork 384
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
Show Homebridge and Homebridge UI versions in update center #2273
Comments
Outdated: New PR opened on branch
|
{{ 'status.homebridge.up_to_date' | translate }} |
v{{ $settings.env.homebridgeVersion }}
For Homebridge UI version:
Line 108 in feba9ac
{{ 'status.homebridge.up_to_date' | translate }} |
v{{ $settings.env.homebridgeUiVersion }}
Still working on where Node.js display is located.
Outdated: New PR opened on branch
|
I was looking at the For Homebridge version: Line 34 in 81ba0bd
should be:
For Homebridge UI version: Line 75 in 81ba0bd
should be:
For Node.js version: Line 147 in 81ba0bd
should be:
|
Closed original PR, as the change should have been made on branch |
Feature Description
What is happening?
Currently, Update Center is showing a grey "Up to Date" string for Homebridge, Homebridge UI, and Node.js:
This doesn't add much to the UI, as it is a light grey and not as eye-catching as the
checkmark
icon (and the icon is a more immediate indicator that all is fine than reading). If there is an update available, it shows a highlighted "Update Available" and thecheck mark
icon is replaced with anupward pointing arrow
icon:What you expect to happen?
When there are no updates available, show the current version for Homebridge, Homebridge UI, and Node.js, instead of "Up to Date".
What problems would this new feature solve?
Primarily it maximizes the real estate on the Status page, by displaying useful information on the UI.
And it reduces the extra clicks, for filling out the
Bug
template, which asks for Homebridge, Homebridge UI, and Node.js versions. 😁The text was updated successfully, but these errors were encountered: