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

feat!: change project name to zwave-js-ui #2650

Merged
merged 29 commits into from
Sep 20, 2022
Merged

feat!: change project name to zwave-js-ui #2650

merged 29 commits into from
Sep 20, 2022

Conversation

robertsLando
Copy link
Member

@robertsLando robertsLando commented Sep 16, 2022

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:

  • 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 prefix changed: zwavejs2mqtt --> z-ui
  • Deprecated zwavejs2mqtt docker tag in favour of the new zwave-js-ui tag

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
@robertsLando robertsLando requested review from AlCalzone and blhoward2 and removed request for AlCalzone September 16, 2022 08:35
@coveralls
Copy link

coveralls commented Sep 16, 2022

Pull Request Test Coverage Report for Build 3068109119

Warning: 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

  • 27 of 149 (18.12%) changed or added relevant lines in 9 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 24.635%

Changes Missing Coverage Covered Lines Changed/Added Lines %
build/webpack.dev.conf.js 0 1 0.0%
src/store/mutations.js 0 1 0.0%
app.ts 0 5 0.0%
bin/www.ts 0 9 0.0%
lib/Gateway.ts 21 45 46.67%
lib/ZwaveClient.ts 0 82 0.0%
Totals Coverage Status
Change from base Build 3061495939: 0.0%
Covered Lines: 3730
Relevant Lines: 15984

💛 - Coveralls

coltenkrauter
coltenkrauter previously approved these changes Sep 16, 2022
Copy link

@coltenkrauter coltenkrauter left a 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 👍

@coltenkrauter
Copy link

Do you have plans to notify the Home Assistant folks so they can update their references to Zwavejs2Mqtt?

https://www.home-assistant.io/integrations/zwave_js/

@robertsLando
Copy link
Member Author

Do you have plans to notify the Home Assistant folks so they can update their references to Zwavejs2Mqtt?

Will ping them both here and on slack too

cc @raman325 @frenck

@frenck
Copy link

frenck commented Sep 16, 2022

I have to comment: Why make the public name so cryptic?

zwave-js-ui is a nice code/slug name to use internally. But that is not something you write on the package of a product. It is also inconsistent, the main project is called Z-Wave JS not zwave-js.

Why not just call this Z-Wave JS UI?

And even JS and UI could be considered technical terms. Z-Wave JS Interface, Z-Wave JS Admin, Z-Wave JS Control Panel, and many others would be less technical.

@robertsLando
Copy link
Member Author

Why not just call this Z-Wave JS UI?

Are you speaking about the project name to use in docs or to use for github repo?

@frenck
Copy link

frenck commented Sep 16, 2022

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 zwave-js-ui makes quite a bit of sense and is fine.

But anything user-facing (e.g., in the UI itself, docs, etc.) that slug makes no sense. zwave-js-ui is not something I would find written like that on a product box ever. Thus is not user focussed or orientated, which is odd for something that a user should consume (a user interface).

Using a slug for the repo/internal zwave-js-ui and using "Z-Wave JS UI" in all user-facing cases would already be more consistent and user-friendly IMHO.

If you think that that comment is wrong, please go ahead with the current :)

../Frenck

@robertsLando
Copy link
Member Author

@frenck I absolutely agree with that. Check my last commit :)

@Petro31
Copy link

Petro31 commented Sep 16, 2022

Eta on when this is rolling out? I'll update the community guides on homeassistant.io when it happens

docs/getting-started/docker.md Outdated Show resolved Hide resolved
docs/getting-started/other-methods.md Outdated Show resolved Hide resolved
docs/index.html Outdated Show resolved Hide resolved
src/App.vue Outdated Show resolved Hide resolved
src/App.vue Outdated Show resolved Hide resolved
static/favicons/site.webmanifest Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/hass_discovery.md Outdated Show resolved Hide resolved
.github/workflows/ci.yml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/bug_report.yml Outdated Show resolved Hide resolved
.github/ISSUE_TEMPLATE/hass_discovery.md Outdated Show resolved Hide resolved
docs/index.html Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
@robertsLando
Copy link
Member Author

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

@frenck
Copy link

frenck commented Sep 16, 2022

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 /old-image file exists and show a warning a user needs to migrate; with e.g., a link to some documentation.

I think it would be hard for people to migrate without proactively informing them.

../Frenck

@coltenkrauter
Copy link

@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.

@robertsLando
Copy link
Member Author

You could push a different version on the old tag, that prints a warning, e.g.:

That would be good, maybe also using an ENV var would be easier.

@frenck
Copy link

frenck commented Sep 16, 2022

maybe also using an ENV var would be easier.

😄

@@ -672,6 +672,41 @@ export default {
} else {
this.$store.dispatch('init', data)

if (data.deprecationWarning) {
Copy link
Member Author

Choose a reason for hiding this comment

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

coltenkrauter
coltenkrauter previously approved these changes Sep 16, 2022
src/App.vue Outdated Show resolved Hide resolved
build/webpack.dev.conf.js Outdated Show resolved Hide resolved
src/App.vue Outdated Show resolved Hide resolved
@robertsLando robertsLando changed the title feat: change project name feat!: change project name Sep 19, 2022
bin/www.ts Outdated Show resolved Hide resolved
docs/troubleshooting/generating-logs.md Outdated Show resolved Hide resolved
@robertsLando robertsLando changed the title feat!: change project name feat!: change project name to zwave-js-ui Sep 20, 2022
@robertsLando robertsLando merged commit 977ea07 into master Sep 20, 2022
@robertsLando robertsLando deleted the feat#2212 branch September 20, 2022 14:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[feat] Change project name
8 participants