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

⚠️ Advanced Notice : V10 Breaking Changes ⚠️ #258

Closed
marcus-j-davies opened this issue Oct 13, 2022 · 1 comment
Closed

⚠️ Advanced Notice : V10 Breaking Changes ⚠️ #258

marcus-j-davies opened this issue Oct 13, 2022 · 1 comment
Labels
never-stale Never stale

Comments

@marcus-j-davies
Copy link
Member

marcus-j-davies commented Oct 13, 2022

So....
We're currently at Version 9 and everything is great and working well.

But here is the thing:
I'm soooo not done 😃

The next major version, V10, will undoubtedly see a massive structural change to the node collection and build process.
in summary, V10 will:

  • Transition the codebase to typescript
  • Transition to using Configuration Nodes for each network.

Transitioning to typescript
Will make it far easier for contributor's to get involved, I have been putting this off for some time, I guess my excuse is, when I first started this project ~ Dec 2019 (back then I was not using ZWave JS) I did not know enough about typescript - I come from a .NET world where everything is type safe by default, so never really thought about it - But now is the time.

Transitioning to Configuration Nodes
Should have been done a long time ago.
This module has been built up by the community, and in fear of breaking installs when an awesome feature has been requested, I have gone about it in a different way - as to not break current installs.

Transitioning to Configuration Nodes, is a huge undertaking, but I feel it has many benefits

  • Unlimited ZWave Networks
  • Smaller memory footprint
  • Less clutter in your flows
  • Overall better internal logic

So.... there it is.
This will take an extremely long time, but I wanted to give users an advanced warning on the unavoidable breaking changes.

Discuss at : #259

Marcus

@zwave-js zwave-js locked as off-topic and limited conversation to collaborators Oct 13, 2022
@marcus-j-davies marcus-j-davies pinned this issue Oct 13, 2022
@marcus-j-davies marcus-j-davies added the never-stale Never stale label Oct 13, 2022
@marcus-j-davies
Copy link
Member Author

Hey everyone,

Just a quick update on V9 progress: it's still in my FOV, and I haven't forgotten about it. Apologies for the delay – But 2023 has been unexpectedly busy in both my professional and private life.

Despite the hectic schedule, I've been keeping V8 maintained, and V9 will soon be getting the attention it deserves. The upcoming release promises to be groundbreaking, thanks to the enhancements from the Z-Wave JS Driver, which I'm eager to include.

Thank you all for your patience and support!

@marcus-j-davies marcus-j-davies changed the title ⚠️ Advanced Notice : V9 Breaking Changes ⚠️ ⚠️ Advanced Notice : V10 Breaking Changes ⚠️ Sep 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
never-stale Never stale
Projects
None yet
Development

No branches or pull requests

1 participant