-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
feat!: change project name to zwave-js-ui
#2650
Conversation
Changes: - GET `/version` api json `z2m` prop has been renamed to `appVersion` - Renamed `Z2M_LOG_MAXFILES` and `Z2M_LOG_MAXSIZE` env vars to `ZUI_LOG_MAXFILES` and `ZUI_LOG_MAXFILES` - `Dockerfile.contrib` `Z2M_BRANCH` and `Z2M_REPOSITORY` renamed to `ZUI_BRANCH` and `ZUI_REPOSITORY` - Default log files and audit file names changed Fixes #2212
Pull Request Test Coverage Report for Build 3068109119Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
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.
I looked through all of your changes and I didn't see any red flags. Good work 👍
Do you have plans to notify the Home Assistant folks so they can update their references to Zwavejs2Mqtt? |
I have to comment: Why make the public name so cryptic?
Why not just call this And even |
Are you speaking about the project name to use in docs or to use for github repo? |
Slug vs. public facing name. Calling the source/repo slug used internally But anything user-facing (e.g., in the UI itself, docs, etc.) that slug makes no sense. Using a slug for the repo/internal If you think that that comment is wrong, please go ahead with the current :) ../Frenck |
@frenck I absolutely agree with that. Check my last commit :) |
Eta on when this is rolling out? I'll update the community guides on homeassistant.io when it happens |
As soon as I get some reviews on this, next week I think :) BTW I will keep pushing image also on old docker tag for a while to give users time to upgrade |
You could push a different version on the old tag, that prints a warning, e.g.: FROM <new image>:<version>
RUN touch /old-image And push that result to the old tag. In the UI you could check if the I think it would be hard for people to migrate without proactively informing them. ../Frenck |
@frenck Great thoughts on the name (slug versus customer facing). I totally agree. Also, I really like your idea about printing a message to people so that they update. |
That would be good, maybe also using an ENV var would be easier. |
@@ -672,6 +672,41 @@ export default { | |||
} else { | |||
this.$store.dispatch('init', data) | |||
|
|||
if (data.deprecationWarning) { |
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.
zwave-js-ui
After many misunderstandings and confusion, we have decided to rename ZwaveJS2MQTT to Z-Wave JS UI.
Many users were confused about 'MQTT' part thinking it needs an MQTT Broker to work when its most important feature is to be a full featured Control Panel UI for Z-Wave JS. We hope that this will make things more clear for everyone.
Fixes #2212
BREAKING CHANGE:
/version
api jsonz2m
prop has been renamed toappVersion
Z2M_LOG_MAXFILES
andZ2M_LOG_MAXSIZE
env vars toZUI_LOG_MAXFILES
andZUI_LOG_MAXFILES
Dockerfile.contrib
Z2M_BRANCH
andZ2M_REPOSITORY
renamed toZUI_BRANCH
andZUI_REPOSITORY
zwavejs2mqtt
-->z-ui
zwavejs2mqtt
docker tag in favour of the newzwave-js-ui
tag