You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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:
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
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
The text was updated successfully, but these errors were encountered: